Every valid Bitcoin block begins with one unusual transaction: the coinbase transaction. It is created by the miner building the block, it does not spend a normal previous UTXO, and it is the mechanism that lets the miner claim the block subsidy plus the transaction fees from the rest of the block.

The name has nothing to do with the Coinbase exchange. In Bitcoin protocol terminology, the coinbase transaction is the first transaction in a block. Bitcoin’s developer documentation also calls it a generation transaction because it is the only transaction allowed to create newly issued bitcoin under the protocol’s subsidy rules.

Every Bitcoin Block Starts With One

Bitcoin’s block-chain rules require every block to contain at least one transaction, and the first transaction must be the coinbase transaction. A block can theoretically contain no ordinary user transactions at all, but it still needs the coinbase transaction so the block has a valid first transaction and the miner can claim any subsidy available at that height.

The Bitcoin developer guide describes the block reward as the combination of two things: the block subsidy and the transaction fees paid by transactions included in that block.

The Coinbase Transaction Does Not Spend a Normal Previous Output

A normal Bitcoin transaction spends one or more previous transaction outputs. The input points backward to an earlier transaction ID and output index. BitcoinVersus.Tech’s UTXO explainer covers that chain in detail.

The coinbase transaction is different because no earlier UTXO exists that contains the newly issued block subsidy. Instead, its input uses a special null previous-output reference. That marks the transaction as the block’s generation transaction rather than an ordinary spend.

The Miner Chooses the Outputs

The outputs of the coinbase transaction tell Bitcoin where the miner’s reward should go. A solo miner might direct the reward to one wallet script. A mining pool typically directs the on-chain block reward to an address or script controlled by the pool and later distributes earnings to individual miners according to its payout system.

That is why a pool miner does not normally receive a tiny piece of the raw block coinbase transaction every time the pool finds a block. The pool tracks contributed work through shares, then performs separate payouts according to its PPS, FPPS, PPLNS, or other accounting method.

Block Reward = Subsidy + Transaction Fees

The maximum value a miner may claim in the coinbase transaction is the current block subsidy plus the fees from the other transactions included in the block. In 2026 the subsidy is 3.125 BTC per block, following the 2024 halving. That subsidy will halve again after another 210,000-block subsidy era completes.

Transaction fees are different. They are not newly created bitcoin. For an ordinary transaction, the fee is the difference between the value of its inputs and the value assigned to its outputs. The miner can claim the aggregate fees from the transactions it includes in the candidate block.

This is one reason hashprice can change even when Bitcoin’s subsidy is unchanged. A block with unusually high fees pays more than a block with almost no fees.

A Miner Cannot Create Extra Bitcoin by Typing a Bigger Number

The coinbase transaction is created by the miner, but the miner does not control Bitcoin’s monetary rules. Every validating node independently knows the maximum subsidy permitted at that block height and can calculate the fees paid by the other transactions in the block.

If the coinbase transaction tries to claim more than the allowed subsidy plus fees, the block is invalid. Other nodes reject it regardless of how much proof of work the miner spent finding the block. That separation is fundamental: miners propose blocks, but full nodes enforce the consensus rules.

The Subsidy Halves Every 210,000 Blocks

Bitcoin started with a block subsidy of 50 BTC. The subsidy halves every 210,000 blocks, roughly once every four years. It fell to 25 BTC, then 12.5 BTC, 6.25 BTC, and 3.125 BTC after the 2024 halving.

The coinbase transaction is where that monetary schedule becomes visible on-chain. Each valid block may create no more than the subsidy allowed for its height. Over many halving eras, the subsidy approaches zero and miner revenue becomes increasingly dependent on transaction fees.

The Coinbase Input Has a Special Data Field

Because the coinbase input does not need to provide a signature unlocking a previous UTXO, its script field can carry special miner-generated data. Modern blocks must include the block height in the coinbase transaction under BIP34 rules, and miners or pools may also use the field for identifiers, extra nonce data, or other permitted information.

This extra data is useful during mining because the miner needs ways to modify the candidate block repeatedly while searching for valid proof of work. Changing coinbase data changes the coinbase transaction ID, which changes the Merkle root, which then changes the block header being hashed.

Why the ExtraNonce Matters

The famous 32-bit nonce field in the Bitcoin block header provides only about 4.29 billion possible values. Modern ASIC hardware can exhaust that range extremely quickly. Miners therefore need a larger search space than the header nonce alone provides.

One method is to change an extraNonce value inside the coinbase transaction. That changes the coinbase TXID and therefore the Merkle root in the block header, creating an entirely new set of header hashes for the SHA-256 ASICs to search.

This is also part of the reason Stratum mining jobs include coinbase-related data. Pools need to give many workers unique search space while still constructing blocks that ultimately pay the pool’s chosen reward outputs.

The Coinbase Transaction Is Part of the Merkle Tree

The coinbase transaction is not separate from the block’s transaction commitment. Its TXID is included with the TXIDs of all the other transactions when the Merkle tree is built. The resulting Merkle root is placed in the 80-byte block header.

Change any transaction—including the coinbase transaction—and the Merkle root changes. That means the block header changes and the miner’s previous proof-of-work search no longer applies to the altered transaction set.

SegWit Added Another Coinbase Responsibility

After Segregated Witness, blocks containing witness data also use the coinbase transaction to carry a witness commitment. This commitment binds the block to the witness data associated with SegWit transactions.

So the coinbase transaction is doing more than paying the miner. In modern Bitcoin it also helps commit additional block data required by consensus rules.

Coinbase Rewards Cannot Be Spent Immediately

A normal confirmed UTXO can generally be spent according to its script conditions. Coinbase outputs have an additional rule: they must mature before they can be spent. Bitcoin’s consensus rules require a coinbase output to wait for at least 100 blocks before it can be used as an input to another transaction.

The reason is chain reorganization risk. If a recently mined block becomes stale during a reorganization, its coinbase transaction disappears from the active chain. Delaying spendability prevents miners from immediately building downstream transactions on rewards that may vanish if their block loses its place in the best chain.

Why Pools Care About Coinbase Construction

For a large mining pool, the coinbase transaction is an operational control point. The pool constructs a block template, chooses transactions, creates reward outputs, inserts required commitments, assigns extraNonce space, and distributes work to connected miners.

The individual ASIC does not usually decide which user transactions enter the block. It hashes work based on the job information supplied by the pool. The pool’s block-template logic and the miner’s share submissions are connected through the mining protocol.

Bitcoin Core Can Expose the Underlying Block Data

Operators running a Bitcoin full node can inspect blocks and transactions through Bitcoin Core RPC. Commands such as getblock, getrawtransaction, and related RPC methods can expose block contents, transaction IDs, outputs, and other data used to study coinbase transactions.

Mining software also relies on node interfaces such as getblocktemplate to obtain the information needed to construct candidate blocks. That is the bridge between Bitcoin’s full-node consensus logic and the specialized software that prepares work for mining hardware.

Coinbase Transactions Explain Where New Bitcoin Actually Comes From

Wallet interfaces can make Bitcoin look as if coins simply move from one account balance to another. Underneath that interface, Bitcoin is a chain of transaction outputs. Almost every spend traces backward through earlier UTXOs until eventually some value traces to a coinbase transaction that introduced a block subsidy into circulation.

That makes coinbase transactions the starting point for newly issued bitcoin. They are where Bitcoin’s programmed monetary schedule intersects with real mining activity.

What Happens After the Final Subsidy?

Bitcoin’s subsidy keeps halving until newly issued amounts eventually round down to zero. When that happens, coinbase transactions will still exist. Miners will still need the first transaction in each block to claim transaction fees and satisfy the block’s required structure and commitments.

The economic difference is that the block reward will then come entirely from fees rather than a combination of new issuance and fees. That long-term transition is one reason transaction-fee markets matter to Bitcoin’s security model.

The Simple Way to Remember It

A normal Bitcoin transaction spends old outputs. A coinbase transaction creates the miner’s claim on the new block reward.

It is always first in the block, can claim no more than the allowed subsidy plus fees, participates in the block’s Merkle commitments, gives miners extra search space, and produces outputs that must mature before they can be spent.

References

• Bitcoin Developers — Block Chain Developer Guide
• Bitcoin Developer Guide — Transactions
• Mastering Bitcoin — Coinbase Transactions

BitcoinVersus.Tech

Advertisement

BitcoinVersus.Tech covers Bitcoin mining, ASIC hardware, mining pools, networking, energy, data centers, semiconductors, and the infrastructure behind proof of work.

Editor’s Note

Bitcoin consensus behavior can change through future protocol upgrades. This article describes the current coinbase-transaction model and should be cross-checked against the exact Bitcoin Core version and consensus rules used in production systems.

We volunteer daily to help keep the information on this platform verifiably accurate. Support our independent research through the support options available on BitcoinVersus.Tech.

BitcoinVersus.tech is not a financial advisor. Content is provided for informational purposes.