The Bitcoin halving explained: a pay cut every 210,000 pages, and nobody has to vote for it
Every 210,000 blocks, the number of new bitcoin paid to the miner of each block is cut in half. It has happened four times, from 50 to 3.125 bitcoin per block. The next one is due at block 1,050,000, which by block arithmetic lands around April 2028.
In the village, whoever writes the next page of the notebook gets paid in brand-new coins. It's a good job. Ben has applied many times.
But the village made a rule at the very start. Every 210,000 pages, the pay for a page is cut in half. No meeting, no vote, no warning letter. Page 209,999 pays the old rate. Page 210,000 pays half.
That's the halving. It isn't an event anybody organises. It's a line in the software that every house checks, and it has worked four times without anyone pressing a button.
What it is
The halving is the point at which the block subsidy, the new bitcoin created with each block, drops by half. Bitcoin Core's code works out the subsidy from the block's height: start at 50 bitcoin, then halve once for every 210,000 blocks. Its comment reads: "Subsidy is cut in half every 210,000 blocks which will occur approximately every 4 years" (Bitcoin Core).
The miner's full pay, the block reward, is that subsidy plus the fees of the transactions in the block. The halving cuts only the first part.
How it works: the four halvings, block by block
Here they are, read from the blockchain itself through the mempool.space explorer.
- The first pay cut, close up. Block 209,999 was mined on 28 November 2012 at 15:01:40 UTC. Its miner received 5,053,620,000 satoshis: 50 bitcoin of subsidy plus 0.5362 in fees (mempool.space). Block 210,000 followed at 15:24:38 UTC. Its subsidy was 25 bitcoin, plus 13.56 in fees (mempool.space). Same day, same network, half the new coins.
- Second halving. Block 420,000, on 9 July 2016 at 16:46:13 UTC. Subsidy from then on: 12.5 bitcoin (mempool.space).
- Third halving. Block 630,000, on 11 May 2020 at 19:23:43 UTC. Subsidy: 6.25 bitcoin (mempool.space).
- Fourth halving. Block 840,000, on 20 April 2024 at 00:09:27 UTC. Subsidy: 3.125 bitcoin (mempool.space).
Now look at the gaps. Measured from the genesis block on 3 January 2009 (mempool.space), the four periods lasted 1,425, 1,319, 1,402 and 1,439 days. At exactly ten minutes a block, 210,000 blocks would take 1,458 days. Every period came in early. Blocks arrived on average every 9.8, 9.0, 9.6 and 9.9 minutes, which is what happens when mining power keeps growing between the difficulty adjustments every 2,016 blocks.
So "every four years" is a rule of thumb. The real rule is a block number.
The next one: an estimate, clearly labelled
The fifth halving comes at block 1,050,000, when the subsidy falls to 1.5625 bitcoin. Here is the arithmetic, not a forecast.
On 18 November 2026 at 21:05:12 UTC, the chain reached block 976,485 (mempool.space). That leaves 73,515 blocks.
- At exactly ten minutes per block: 510 days, which lands around 12 April 2028.
- At the 9.95-minute average seen since block 840,000: a few days earlier, around 9 April 2028.
Our estimate: around April 2028. The real date depends on how fast blocks come between November 2026 and then, and nobody can schedule that.
Why it matters
- Miners take the cut. Overnight, half of the new coins per block disappear from their income. Miners whose costs were already close to their earnings may switch off.
- New supply slows. Fewer new coins per block means the total creeps towards its cap more slowly. Why the cap is just under 21 million is in "Why only 21 million bitcoin?".
- Fees have to grow up. The white paper says that eventually "the incentive can transition entirely to transaction fees" (Nakamoto, 2008). On the evening of 18 November 2026, fees made up less than 1% of the pay in the 15 blocks we checked (mempool.space). That gap is one of Bitcoin's big open questions.
Where people get it wrong
- "The halving halves the number of bitcoin." It halves the new coins per block. Existing coins are untouched.
- "It happens every four years on a set date." It happens at a set block height. The date drifts with block times.
- "The halving cuts fees too." Fees are set by the people sending payments. Only the subsidy halves.
- "Someone decides when to halve." Nobody does. Every node checks the subsidy against the block height, and rejects a block that pays its miner too much.
- "The halving moves the price." Nothing in the code mentions a price. Anyone who tells you what a halving will do to it is guessing, or selling.
The sting: do the countdown yourself
Open a block explorer and note the current block height. Subtract it from 1,050,000. Multiply by ten minutes. That's your own halving estimate, and it's as good as anyone's.
Then watch for the stranger at the gate with his "halving countdown" and his special offer that expires at block 1,050,000. The block will arrive on time. His offer won't age as well.
Frequently asked questions
What is the Bitcoin halving?
The halving is the point, every 210,000 blocks, when the number of new bitcoin paid to the miner of each block is cut in half. It's written into Bitcoin's software and checked by every node.
When were the Bitcoin halvings?
At block 210,000 on 28 November 2012, block 420,000 on 9 July 2016, block 630,000 on 11 May 2020 and block 840,000 on 20 April 2024. The subsidy went from 50 to 25, 12.5, 6.25 and 3.125 bitcoin per block.
When is the next Bitcoin halving?
At block 1,050,000. Based on the block height on 18 November 2026 and an average of about ten minutes per block, it's expected around April 2028. That's an estimate from block arithmetic, not a fixed date.
Why don't halvings happen exactly every four years?
Because the rule counts blocks, not days. Blocks have arrived slightly faster than one every ten minutes on average, so each of the first four periods was shorter than four years.
Does the halving affect transaction fees?
Not directly. The halving cuts only the newly created coins in each block. Fees are paid by senders and depend on how much space they need and how busy the network is.
Sources
- Bitcoin Core source code, src/validation.cpp (GetBlockSubsidy)
- mempool.space API, Bitcoin block 209,999 (28 November 2012)
- mempool.space API, Bitcoin block 210,000 (28 November 2012)
- mempool.space API, Bitcoin block 420,000 (9 July 2016)
- mempool.space API, Bitcoin block 630,000 (11 May 2020)
- mempool.space API, Bitcoin block 840,000 (20 April 2024)
- mempool.space API, blocks 976,471 to 976,485 (18 November 2026)
- mempool.space API, genesis block 0 (3 January 2009)
- Satoshi Nakamoto, Bitcoin: A peer-to-peer electronic cash system (2008), section 6

