Halving: block subsidy and issuance schedule

Block height

Use a dot or comma as the decimal separator; separate thousands with a space.

Enter an integer height of 0–6 930 000. Empty or invalid input hides the result.

Use loaded height Reload network data

Loading…

Source of loaded height: —

Network response assembly time (UTC): —

Last response (UTC): —

Bitcoin’s supply is limited because a valid block may create new units only according to a declining block subsidy schedule. Every fully validating node checks this rule independently. The familiar 21 million is the rounded result of this schedule, not a number stored in one company’s database.

A miner may include a coinbase transaction in a valid block. Its total outputs may not exceed the issuance subsidy allowed at that block height plus transaction fees. Fees transfer existing bitcoin; only the subsidy creates new units. A block with an excessive coinbase reward is invalid.

On mainnet the subsidy starts at 50 BTC and halves every 210 000 blocks, truncating to whole satoshis. The last nonzero block is at height 6 929 999; from 6 930 000 the subsidy is zero. Remaining issuance uses the exact theoretical total, not the rounded 21 million.

The sum includes every permitted subsidy from height 0 through the selected block. It is neither circulating nor spendable supply: it includes the genesis block’s unspendable 50 BTC and does not subtract unclaimed subsidies or lost coins. Fees are not new issuance.

We project a date only for the loaded height: response assembly time plus remaining blocks times 10 minutes. It is neither a block’s mining time nor a fixed deadline. Data from mempool.space or fallback Blockchain.com may be cached; actual block intervals vary.