47.44 bitcoin have been removed from spendable supply since May 2020
A question we left open is now closed at the satoshi. From block 629,039 on 5 May 2020 through block 969,785 on 4 October 2026, the gap between the issuance schedule and the coins the protocol can still spend grew by exactly 47.44449633 BTC.
When we published how many bitcoin exist, the gap at block 969,785 was 230.12 BTC. Up to May 2020 that figure lines up with the 182.67920835 BTC Fabian Jahr measured at block 629,038 [1]. The remaining 47.44 BTC were a residual we had not yet broken down. This count does that, from a complete read of the interval on our full node.
What the 340,747 blocks contain
| Item | BTC | Satoshis | Episodes |
|---|---|---|---|
| OP_RETURN outputs | 47.44107633 | 4,744,107,633 | 164,860 |
| Unclaimed reward | 0.00342000 | 342,000 | 1 |
| Increase over the interval | 47.44449633 | 4,744,449,633 | 164,861 |
| Jahr's baseline, block 629,038 | 182.67920835 | 18,267,920,835 | — |
| Total | 230.12370468 | 23,012,370,468 | — |
230.12370468 BTC matches the 230.12 we had already published, once that earlier figure is taken to two decimal places [2]. It is not an independent satoshi-level reconciliation with a UTXO-set snapshot at those exact heights: that would require a full unspent-set total at 629,038 and at 969,785, which we have not produced. What is exact is the increment over this interval, summed in integer satoshis.
Unclaimed reward is a rounding error in the story: 0.00342 BTC, or 0.007% of the increase. The other 47.44107633 BTC were assigned to outputs the protocol marks unspendable with OP_RETURN.
How the count was done
Each block in the range was read on our full node. We did not interpolate between weekly snapshots. For every height, unclaimed reward is subsidy plus fees minus the sum of every coinbase output, in integer satoshis [3]. Separately, we added the positive value of every output whose script starts with OP_RETURN or exceeds 10,000 bytes, the threshold Bitcoin Core treats as unspendable [4]. If an output meets both tests, it is counted once, as OP_RETURN. Unspendable coinbase outputs are included in the coinbase sum before unclaimed reward is calculated, so they are not counted twice.
No output in this interval is booked only for being oversized. One output, in block 949,973 on 18 May 2026, has a 184,309-byte script and 0.00021000 BTC, and it was already an OP_RETURN.
The parser was checked against a fully decoded read of every transaction in blocks 629,039, 910,513 and 911,520: the hash, the transaction count, the coinbase identifier, its value and every unspendable episode matched. Before the full range was run, the 1,008-block window from 910,513 to 911,520 — the one in which our weekly snapshots had shown a jump of about 9 BTC — came to 9.00298447 BTC, all of it OP_RETURN. Across the 340,747 blocks, the per-block totals and the per-episode list agree, with no mismatches and no duplicates.
The yearly totals, the monthly breakdown, the 25 largest episodes and the unclaimed-reward case are available as CSVs. Anyone with a complete Bitcoin Core node can repeat the count at the same heights.
The gap did not grow steadily
2025 is not the heaviest year, even though it contains the 9 BTC output. 2021 is, at 15.15104597 BTC. 2020, which in this series only starts on 5 May, adds 8.37831462 BTC, close to 2022. Through 4 October, 2026 adds just 0.03367736 BTC.
| Year (UTC) | BTC removed | Episodes | Note |
|---|---|---|---|
| 2020 | 8.37831462 | 1,776 | From 5 May |
| 2021 | 15.15104597 | 251 | |
| 2022 | 8.64424353 | 17,019 | |
| 2023 | 4.65129137 | 59,449 | |
| 2024 | 0.87180272 | 4,827 | |
| 2025 | 9.71412076 | 58,478 | |
| 2026 | 0.03367736 | 23,061 | Through 4 October |
Months are grouped by the UTC time in each block header. The full monthly series, with the first and last height of each month, is in the monthly totals CSV. Four months hold most of the story:
| Month (UTC) | BTC removed | Episodes |
|---|---|---|
| February 2021 | 14.06143835 | 72 |
| August 2025 | 9.01184062 | 1,186 |
| October 2020 | 8.14714891 | 76 |
| February 2022 | 7.85935269 | 653 |
February 2021, not the month of the 9 BTC output, is the heaviest in the series: 14.06143835 BTC left spendable supply in 72 outputs.
That single month is 29.6% of the whole increase since May 2020. August 2025, at 9.01184062 BTC, is almost entirely one 9 BTC output; the other 1,185 episodes in the month add 0.01184062 BTC. February 2022 looks different again: 7.85935269 BTC across 653 outputs, including block 723,947 on 18 February 2022 at 23:33 Madrid time, which packs 2.98209943 BTC into 141 OP_RETURN outputs.
The cumulative curve makes those four steps obvious. Between them, the pace is much lower. 2023 adds 4.65129137 BTC, but it does so in 59,449 outputs, almost all of them tiny: heavy OP_RETURN use, not a few large burns.
The 9 BTC output, and the others that matter
Only two outputs in the interval are 1 BTC or larger. The largest is the one already visible in the weekly snapshots: in block 911,416, at 05:19 Madrid time on 24 August 2025, a transaction assigned 9 BTC to output 2, with a 6-byte OP_RETURN script. The transaction id is 613f59897065a4ea8999c79233d0fdb4b252245838ca5855c687e5620dd32179. We also checked it against the raw transaction and the block hash, separately from the range count. We do not attribute that output to anyone. The chain records how much was burned, in which block and in which transaction; it does not record who did it, or why.
The second, 1.888 BTC, is in block 653,902, at 05:11 Madrid time on 23 October 2020, transaction 0122d2f239ae53e8655d83ff0a75bc60f4ffff71554363103fe09787b80cb12b. The rest of the list, down to 0.1 BTC, is in the CSV of the 25 largest episodes. Fifteen of those 25 fall between 13 and 24 February 2021.
The 65 outputs of 0.1 BTC or more add up to 30.14508006 BTC, 63.5% of the increase. At the other end, the median of the 164,860 OP_RETURN outputs is 546 satoshis. Most episodes move very little value; a relatively small number of large ones carry the total.
A single unclaimed reward
In 340,747 blocks we found unclaimed reward only once. It is in block 956,984, at 05:04 Madrid time on 7 July 2026. The subsidy that day was 3.125 BTC and the fees were 0.00342 BTC. The coinbase paid exactly 3.125 BTC and left the 0.00342 BTC of fees unclaimed. The coinbase transaction id is 8aaecf02aa4e8c82728a4aff6b7d80dca54798b1774d24a14451350cfd752f1c. The block amounts are in the unclaimed-reward CSV.
That accounting does not assign an intent. What the chain does settle is the arithmetic: the budget was subsidy plus fees, and the coinbase output matched the subsidy.
What this figure does not say
It does not include bitcoin lost because a key was forgotten, a disk was wiped or an inheritance was left without a plan. Those coins remain in the unspent set, and the node adds them up. This total is only what the protocol itself can no longer spend.
It is also not an attribution. An OP_RETURN output does not name its author, and an unclaimed reward does not, on its own, tell an error from a choice. We do not fill that in.
There is a smaller limit, which we record so it is not swept aside. In our weekly UTXO-set snapshots, the change between 17 and 24 August 2025 (blocks 910,512 and 911,520) is 9.00298433 BTC, 14 satoshis less than the 9.00298447 BTC of the block-by-block count from 910,513 to 911,520. We have not adjusted the result to mimic that weekly series, which we do not treat as an exact reference. The figures in this article come from the sweep.
Sources
Labelled by type.
- Fabian Jahr, "Where are the coins?", 8 May 2020, republished at Bitcoin Words. The 182.67920835 BTC baseline at block 629,038. (Secondary relative to a node count: analysis by a Bitcoin Core developer; we use his figure as the base to which our increment is added)
- NodeWitness, "230.12 Bitcoin Were Issued That No One Can Ever Spend", UTXO-set count at block 969,785, and the note that the 47.44 BTC after May 2020 had not been broken down. (Primary, earlier data of our own)
- Bitcoin Core,
GetBlockSubsidyinvalidation.cpp. The issuance schedule that sets each block's subsidy. (Primary, reference code) - Bitcoin Core,
IsUnspendableinscript.h. An output is unspendable if its script starts with OP_RETURN or exceeds 10,000 bytes. (Primary, reference code) - NodeWitness, block-by-block count on our full node, heights 629,039–969,785 (340,747 blocks), completed on 20 November 2026. Totals and breakdowns in the CSVs for this article. (Primary, our own data)
The Bitcoin supply count, measured on our full node, is on the supply page, alongside how many bitcoin exist.
More in Supply and holders
Last updated: November 20, 2026