Bitcoin halving history: open data
The four halvings that have happened and the fifth projected one, with exact block height, date and the reward before and after. Published in JSON and CSV under a CC BY 4.0 licence, so anyone can use it with attribution.
Download
Two formats, the same content. No sign-up and no conditions beyond attribution.
The data
| Halving | Date | Block | Reward before | Reward after |
|---|---|---|---|---|
| 1st | 2012-11-28 | 210,000 | 50 BTC | 25 BTC |
| 2nd | 2016-07-09 | 420,000 | 25 BTC | 12.5 BTC |
| 3rd | 2020-05-11 | 630,000 | 12.5 BTC | 6.25 BTC |
| 4th | 2024-04-20 | 840,000 | 6.25 BTC | 3.125 BTC |
| 5th | estimated around 2028 | 1,050,000 | 3.125 BTC | 1.5625 BTC |
The fifth row is an estimate, not a settled fact, and it is flagged as such in the files through the estimado field. The block height is exact — a halving always occurs every 210,000 blocks — but the date depends on the real pace of mining, which varies with hashrate.
Where it comes from
From the blockchain itself. There is no intermediate source to verify and no price estimate involved: the block reward is written into the protocol and the heights are arithmetic. Anyone can check every row against a block explorer in under a minute.
That is the reason for publishing it: this is information that circulates everywhere, almost always without a source, often with dates that disagree with each other, and rarely in a format you can drop into a spreadsheet or a script.
What each file contains
| Field | Type | What it is |
|---|---|---|
numero | integer | Halving order, 1 to 5 |
fecha | text YYYY-MM-DD | Day the block was mined. Empty for the projected one |
bloque | integer | Exact height at which the reduction applies |
recompensa_antes_btc | decimal | Bitcoin issued per block before the halving |
recompensa_despues_btc | decimal | Bitcoin issued per block after it |
estimado | boolean | True only for the fifth, whose date is a projection |
Licence and attribution
The data is published under Creative Commons Attribution 4.0. You may use, modify and redistribute it, including commercially, as long as you credit the source.
Crypto Terminal (2026). Bitcoin halving history. CC BY 4.0.
https://terminalcripto.com/en/data/
What it does not include, and why
No prices. Tables circulate that add Bitcoin's quote at each halving and the subsequent appreciation, but those figures depend on which exchange and which hour you take as reference, and the differences between sources are large. Mixing them with on-chain data in the same file would give a false impression of precision.
Nor are there projections beyond the fifth halving. They can be calculated by adding 210,000 blocks, but date uncertainty grows with each cycle until it stops being useful.
What it is for
For any analysis that needs to place events relative to the issuance cycle: days elapsed since the last halving, comparison across normalised cycles, or simply a reliable reference when writing about the subject. If you want to understand what these numbers mean, the explanation is in the halving cycle guide, and the live countdown is in the tool.
Frequently asked questions
Can I use this data on my site or in an article?
Yes. It is licensed under Creative Commons Attribution 4.0, which allows use, modification and redistribution including commercially, with the single condition of crediting and linking the source.
Where do the dates come from?
From the Bitcoin blockchain. Each halving occurs at a fixed block height — every 210,000 blocks — and the date is the day that block was mined, verifiable in any explorer.
Why is the fifth halving date an estimate?
Because the block height is known (1,050,000) but how long it takes to get there depends on the pace of mining. The average is ten minutes per block, but it varies with hashrate, so the date shifts.
Why does the file not include Bitcoin's price at each halving?
Because price depends on which exchange and hour you take as reference, and differences between sources are considerable. Mixing that with exact on-chain data would give a false impression of precision.
How often is it updated?
It only changes when a halving occurs, roughly every four years. The date of the last revision is inside the JSON file itself, in the actualizado field.
What is the difference between the JSON and the CSV?
None in content. The JSON additionally carries metadata such as licence, source and a note about the estimated halving; the CSV is a flat table meant to be opened directly in a spreadsheet.
How many halvings will there be in total?
Thirty-two, until the block reward reaches zero around the year 2140. This dataset covers only the four that have happened and the next one, because beyond that the uncertainty in the dates grows too large.
Want the full cycle live?
Crypto Terminal computes it live alongside the other modules, with confluence across 6 timeframes.
Get it on Google PlayFree companion book: Technical Analysis of Crypto-Assets: Crypto Terminal · Edición en español