Coinbase Transaction

Definition: A coinbase transaction is the first transaction in each valid Bitcoin block. It has a special input that does not spend a previous transaction output, and it creates outputs that claim the block subsidy and the fees from transactions included in that block. The term is unrelated to Coinbase, the cryptocurrency exchange.13

PositionFirst transaction in a Bitcoin block1
Special inputOne input with a null previous output; it does not spend an ordinary UTXO.3
What it may claimThe allowed block subsidy plus the fees from transactions in that block.1
Coinbase maturityOutputs become spendable after 100 confirmations, counting the block that created them.1
DirectoryBitcoin Directory

What the coinbase transaction does

Bitcoin blocks contain one or more transactions, and the coinbase transaction must come first. Its special input is not a payment input: it does not refer to an unspent output created by an earlier transaction. Bitcoin Core recognizes a coinbase transaction by its single input and null previous outpoint. That makes it a distinct transaction type used only inside a block, rather than a normal payment a wallet can broadcast on its own.13

The transaction’s outputs direct the miner’s claim to one or more spending conditions. A miner may choose how to arrange those outputs, but the total value claimed cannot exceed the amount permitted by Bitcoin’s rules. Nodes validate the coinbase along with the rest of the block; a block that overclaims the reward is invalid even if its proof of work is otherwise acceptable.14

Subsidy and transaction fees

The coinbase transaction collects two different things. The block subsidy is the amount of new bitcoin a valid block may create under the issuance schedule. Transaction fees are the difference between the value consumed by a transaction’s inputs and the value assigned to its outputs; the miner can claim the fees from transactions that the block includes. Together, the subsidy and those fees make up the block reward. Fees transfer value already in circulation, while the subsidy is new issuance.1

This distinction matters when reading a block explorer. The first transaction may show a value larger than the current subsidy because it also collects fees. The displayed total is not all newly created bitcoin. To understand a particular block’s reward, compare its coinbase outputs with the subsidy permitted at that block height and the fees paid by the other transactions it contains.1

The 100-block maturity rule

Coinbase outputs have a special maturity delay: they become spendable after 100 confirmations, counting the block that created them. This gives the chain time to resolve a short-lived fork. If a block becomes stale and is no longer part of the accepted chain, its coinbase transaction and reward do not remain spendable on the competing history. The delay reduces the risk that a miner spends a reward from a block that is later removed by a reorganization.1

Maturity is not the same as simply seeing a transaction in a block. A coinbase output can appear in a block and be visible to explorers while still being unavailable to spend. Wallets and mining software need to track the output’s block height and maturity status before treating it as spendable balance.

Block height and coinbase data

The coinbase input contains a script field that can carry data. BIP 34 changed the block format so that a version 2 block’s height is encoded as the first item in the coinbase input’s script. This helps identify the height of the block that contains the transaction. The height is useful context, but it is not a globally unique block identifier: competing branches can contain different blocks at the same height. A block hash is used to distinguish them.21

Miners may place other data in the coinbase field, subject to the rules in force. This is why coinbase inputs sometimes contain text or mining-related metadata. The field’s presence does not turn the transaction into a message system, and arbitrary data in it does not change the transaction’s role: it remains the block’s special reward-claim transaction.

How it differs from a Coinbase account

“Coinbase” here is a protocol term, not a reference to the Coinbase exchange. A coinbase transaction is produced as part of constructing a Bitcoin block. It is not a deposit, exchange credit, or transfer from the company. The shared name can be confusing, so context matters: discussions of blocks, subsidies, fees, and mining refer to the transaction type.

History

  • January 2009: The first Bitcoin block included a coinbase transaction, beginning the chain’s block-reward mechanism.1
  • July 6, 2012: BIP 34 was assigned to specify a block-height commitment in the coinbase input.2
  • March 2013: BIP 34’s version 2 block rules were deployed; the BIP records block 227,835 as the last version 1 block.2

Page updated: November 10, 2026.

Related Terms

Related Articles

See Also

Sources

  1. Bitcoin Developer Guide. “Block Chain.” Accessed November 10, 2026. Bitcoin Developer Guide.
  2. Bitcoin Improvement Proposals. “BIP 34: Block v2, Height in Coinbase.” Assigned July 6, 2012; status: deployed. Accessed November 10, 2026. BIP 34.
  3. Bitcoin Core Developers. “Transaction.” GitHub. Accessed November 10, 2026. Bitcoin Core source code.
  4. Bitcoin Core Developers. “Validation.” GitHub. Accessed November 10, 2026. Bitcoin Core source code.