Coinbase Maturity

Coinbase maturity is the Bitcoin consensus rule that newly mined coins cannot be spent immediately. The output of a coinbase transaction — the special transaction that pays a miner the block subsidy plus collected fees — must wait 100 additional blocks before it becomes spendable. Because the originating block counts as the first confirmation, the reward is effectively unlocked at 101 confirmations, roughly 16 to 17 hours at the 10-minute block target. Unlike most wallet-level waiting periods, this one is enforced by every full node: a transaction spending an immature coinbase output is invalid by consensus and will be rejected outright.

Why the delay exists

The maturity rule protects the network and downstream spenders against chain reorganizations. Every block a miner finds sits on one particular branch of chain history. If a competing branch overtakes it, that block — and the brand-new coins it created — simply ceases to exist on the winning chain. Ordinary transactions that get reorganized out can usually be re-mined in a later block, because the coins they spend still exist. A reorganized-away coinbase output cannot: the coins were never created on the surviving chain. Without a maturity window, someone could accept freshly minted coins as payment and then watch them evaporate in a shallow reorg, with no way to recover. Forcing a 100-block wait makes it astronomically unlikely that a spent reward will be erased, since reorgs deeper than a handful of blocks are extraordinarily rare on Bitcoin.

What miners actually see

In pool dashboards and mining software, freshly earned rewards appear as an immature or pending balance until the threshold passes, then move to confirmed and spendable. This is normal and is not a stuck payout. The rule also shapes how pools operate: a mining pool cannot distribute a block's proceeds from the block itself until maturity, so pools either front payouts from working capital or delay crediting until the reward matures. If a pool's block later gets orphaned, that immature balance is clawed back — one reason pool terms distinguish between found blocks and matured blocks.

The solo miner's edge case

For a solo miner — including a lottery-style Bitaxe pointed at a solo pool — coinbase maturity is the fine print on the dream scenario. Hit a block and the full block reward lands in your coinbase output, but you will wait those ~17 hours before a single satoshi can move. Node runners verifying their own rewards will see the coins in the UTXO set immediately, flagged as immature. It is a good habit to wait well past maturity before treating the funds as settled, and to remember that the maturity clock is counted in blocks, not hours — a slow-block day stretches the wait.

Developer and record-keeping corners

The maturity rule surfaces in a few places beyond the pool dashboard. Anyone experimenting on a private regtest network discovers it immediately: after mining a block, the reward is unspendable until 100 more blocks exist, which is why test scripts habitually generate 101 blocks before doing anything with coins. Wallet software must track immature outputs as a distinct balance category, and block explorers mark young coinbase outputs accordingly. For record-keeping, the distinction matters too: the coins exist on-chain from the moment the block is found — with a timestamp and a market value — even though they cannot move yet, so a mining operation's books will typically recognize the reward at the block's date rather than at maturity. None of this changes the rule itself; it just means every serious tool in the stack has to model it correctly.

The rule applies specifically to the coinbase transaction at the top of every block. Learn more about the reward itself in Block Subsidy, and about the extra search space miners hide inside the coinbase in Extranonce.