The Coinbase Transaction: How Miners Get Paid

The coinbase transaction is the first transaction in every Bitcoin block: it has one placeholder input, creates the new coins, collects the fees, and its outputs say who gets paid. This explainer covers its input and coinbase field, the subsidy (3.125 BTC since the April 2024 halving) plus fees, why it normally has more than one output, and the 100-block wait.

Category: Mining and the Network · Published 2026-10-28

Editorial review complete · technical review pending · sources under review · time-sensitive: revisit periodically

What does this mean?Editorial review covers clarity and neutrality. Technical, security, and source reviews indicate whether an article's material claims were checked against relevant authoritative material. A source link being available does not by itself mean every claim has been verified. A reviewed status means the article's material claims were examined; it does not mean the article is exhaustive or that future protocol, market, or software changes cannot make it outdated.

The first transaction in every block

Open any Bitcoin block and look at the very top of its list of transactions. The first one is always special. It is called the coinbase transaction, and it is the transaction that pays the block's reward to the miner, or the mining pool, that found the block.1

Every other transaction in a block moves coins that already exist from one owner to another. The coinbase transaction is different: it is where brand-new bitcoin is created and where the block's reward is collected. There is exactly one coinbase transaction per block, no more and no less, and it always sits in first place.2

Why it has no normal inputs

A normal Bitcoin transaction has inputs and outputs. The inputs point back to coins you received earlier and prove you are allowed to spend them; the outputs say where those coins go. You can only send what you already own: a normal transaction whose outputs are worth more than its inputs is rejected.1

The coinbase transaction breaks that rule on purpose. It creates coins that did not exist a moment ago, so there is no earlier payment for it to point back to. Instead of a real input, it carries exactly one placeholder input that references nothing: a previous transaction ID of all zeros and an output number of 0xffffffff, which every node recognizes as meaning this is a coinbase.3

That placeholder input has a useful side effect. Its script, often called the coinbase field, can hold up to 100 bytes, and apart from the block height it can be any data the miner likes.3 Miners put things there such as:

  • The block height, which the rules have required since March 2013 (BIP34) so that each coinbase transaction is unique.4
  • An extra nonce: extra room to vary the block while searching for a valid hash.3
  • Short tags or messages, such as a name. The coinbase field of block 973,413, for example, holds its height and a short tag naming the solo pool that mined it.5

Subsidy plus fees: the two halves of the reward

A miner's reward is made of two separate parts, and the coinbase transaction combines them into its outputs.1

  • The block subsidy: freshly created bitcoin, 3.125 BTC per block since the April 2024 halving.6 The subsidy is cut in half every 210,000 blocks, roughly every four years, in an event called the halving, and it steps down toward zero.2
  • The transaction fees: the leftover value that the senders of all the other transactions in the block chose to pay, meaning the difference between each transaction's inputs and outputs. The miner collects the total.1

So the most a miner can claim is the subsidy plus every fee in the block, and a coinbase that pays out more makes the whole block invalid.2 As the subsidy keeps halving over the coming decades, fees are meant to carry a growing share of the reward, and in the end all of it. The subsidy is also the only way new bitcoin is ever created, which is what ties Bitcoin's limit of just under 21 million coins directly to this one transaction.6 What happens as the subsidy approaches zero looks further ahead.

More than one output

The coinbase transaction has exactly one input, but it can have many outputs, and it normally has more than one. A block that contains SegWit transactions must commit to their witness data in an extra output of the coinbase, one whose script begins with OP_RETURN, so it can never be spent.7 A pool can also split the reward across several addresses. Block 973,413, mined through a solo pool on 27 October 2026, shows both: its coinbase pays 3.07689054 BTC to one address and 0.06279368 BTC to another, and carries a zero-value witness commitment as a third output.5

It has nothing to do with the company Coinbase

The shared name causes confusion, so let's be blunt: the coinbase transaction and the exchange company named Coinbase are completely unrelated.

In Bitcoin, coinbase is a technical term. Bitcoin's developer documentation uses it for this reward transaction and for its special input, the coinbase field described above.3 The exchange is a separate company that shares the word and nothing else. When Bitcoin's own software or a block explorer says coinbase, it means the miner's reward transaction, never the exchange.

Why it matters for solo mining

Here is where the coinbase transaction becomes very concrete. Whoever builds a candidate block builds its coinbase transaction, which means they choose the payout addresses in its outputs. A solo miner running its own node writes its own address; in pooled mining, the pool's server builds the coinbase, usually paying the pool, and sends your miner only the pieces it needs to hash.8 Whoever's address is written there is the one who gets paid if that block is found.

This payout is not an afterthought bolted on later. The coinbase transaction is folded into the block's merkle root, the single fingerprint of every transaction that sits inside the block header being hashed.1 In other words, the reward destination is locked into the very thing the miner is racing to solve: change it afterward and the proof of work no longer matches.

For a solo miner with its own node, that address is simply their own wallet: find a block, and the coinbase pays the subsidy and fees straight to them, with no custodian holding the funds. A solo pool that writes each miner's own address into the coinbase works the same way, less any fee it takes as its own output.

The 100-block wait before it can be spent

There is one honest caveat worth knowing. Coins from a coinbase transaction cannot be spent right away: the rules require them to mature for 100 blocks before they can move.1 Since a block arrives roughly every ten minutes on average, that wait usually works out to something like sixteen or seventeen hours.

The reason is safety. Occasionally two miners find a block at almost the same moment and the network briefly disagrees about which one counts; one of those blocks ends up stale and is dropped. The maturity delay makes sure a freshly minted reward cannot be spent until its block is buried deep enough that it is very unlikely to be replaced. If a block does end up stale, its coinbase pays nothing: the reward only exists on the chain the network keeps.1

FAQ

Is the coinbase transaction the same as the Coinbase exchange?

No. The coinbase transaction is Bitcoin's built-in reward transaction, and coinbase is the word Bitcoin's own software and documentation use for it. The exchange named Coinbase is a separate company that shares the word and nothing else.

Where do the coins in the block subsidy come from?

They are newly created by the coinbase transaction itself. Unlike a normal payment, the subsidy has no previous owner. It is the one and only way new bitcoin comes into existence, and the halving schedule keeps the total supply just under 21 million coins.

How much does a miner earn per block?

At most the block subsidy plus all the transaction fees in that block. The subsidy has been 3.125 BTC since the April 2024 halving and halves every 210,000 blocks. The fee portion varies from block to block depending on how much the senders chose to pay, and any pool fee comes out of the total.

Why does a miner have to wait before spending the reward?

Coinbase rewards must mature for 100 blocks, about 16 to 17 hours on average, before they can be spent. This guards against spending a reward from a block that later turns out to be stale, which can happen when two blocks are found at nearly the same time.

Who decides which address the reward is paid to?

Whoever builds the block. A solo miner with its own node writes its own address; in a pool, the pool's server builds the coinbase. The payout addresses sit in the coinbase outputs, and the coinbase is committed into the block header through the merkle root, so the payout cannot be changed afterward without redoing the work.

Key takeaways

  • Every block's first transaction is its coinbase transaction, and a block has exactly one.
  • It has one placeholder input that points at nothing, plus a free-form coinbase field holding the block height, an extra nonce and often a short tag.
  • Its outputs can claim at most the block subsidy (3.125 BTC since the April 2024 halving) plus the block's transaction fees.
  • It normally has more than one output, such as the SegWit witness commitment or a pool's share of the reward.
  • Coinbase coins cannot be spent until 100 blocks have passed, and the name has nothing to do with the exchange called Coinbase.

Sources

  1. Bitcoin Developer Guide, Block Chain: the first transaction must be the coinbase (generation) transaction collecting the subsidy plus fees; its outputs cannot be spent for 100 blocks; stale blocks and forks; the merkle root in the header; outputs worth more than inputs are rejected; the two-week (1,209,600-second) retarget — Bitcoin Project (developer.bitcoin.org)
  2. Bitcoin Core source, validation.cpp: the first transaction must be the coinbase and no other may be (bad-cb-missing, bad-cb-multiple); GetBlockSubsidy halves the 50 BTC subsidy every 210,000 blocks; a coinbase paying more than subsidy plus fees makes the block invalid (bad-cb-amount) — Bitcoin Core project (GitHub)
  3. Bitcoin Developer Reference, Transactions: the coinbase input (one input, a 32-byte null hash and index 0xffffffff), the coinbase field of up to 100 bytes holding the BIP34 height, an extra nonce and arbitrary data — Bitcoin Project (developer.bitcoin.org)
  4. BIP34, Block v2, Height in Coinbase: the block height as the first item of the coinbase scriptSig, to enforce block and transaction uniqueness; the last version-1 block was 227,835 on 24 March 2013 — Bitcoin Improvement Proposals (GitHub)
  5. Block 973,413 (27 Oct 2026, mined through a solo pool): coinbase with one null input and three outputs, 3.07689054 BTC and 0.06279368 BTC to two addresses plus a zero-value witness commitment, totalling the 3.125 BTC subsidy and 0.01468422 BTC of fees — mempool.space
  6. Controlled supply: the subsidy halves every 210,000 blocks, total supply slightly less than 21 million, block 840,000 reached on 2024-04-20 with a 3.125 BTC subsidy, miners paid by fees alone once issuance ends — Bitcoin Wiki
  7. BIP141, Segregated Witness (consensus layer): the witness commitment recorded in an OP_RETURN scriptPubKey (an output) of the coinbase transaction, required when a block contains witness data — Bitcoin Improvement Proposals (GitHub)
  8. Bitcoin Developer Guide, Mining: solo mining (large payments, higher variance) versus pooled mining (small payments, lower variance); shares against an easier pool target; the block reward paid to the pool, which pays miners per share; getblocktemplate and Stratum, where the pool supplies the coinbase — Bitcoin Project (developer.bitcoin.org)

Some specific claims in this article are scheduled for further source review; citations may be expanded (see our editorial policy).