Bitcoin transaction confirmations: how many you need and UTXOs

Bitcoin transaction confirmations are the blocks added to the chain on top of the block that holds your payment. Once a transaction lands in a block it has one confirmation; the next block makes it two, and so on. The protocol sets no required number — the receiver decides how long to wait. The classic benchmark is 6 confirmations, roughly an hour, while exchanges often credit sooner: Kraken waits for three. Below: where these numbers come from, how bitcoin's "coins" (UTXOs) work, and why they drive your fee.

What is a bitcoin transaction confirmation?

When you send bitcoin, your wallet broadcasts a signed transaction to the network. It first sits in the mempool, the queue of unconfirmed payments (covered in our guide to mempool fees). That is zero confirmations: the payment is visible but not yet protected by any proof of work.

When a miner includes it in a block, it gets its first confirmation. Every new block references the previous one, so to rewrite your payment an attacker would have to re-mine your block and every block after it, then outpace the rest of the network. Each extra block makes that more expensive. The rule of thumb: confirmations = current block height − the transaction's block height + 1.

A block arrives every 10 minutes on average, but that is only an average. Intervals are random: the next block can come in one minute or in thirty. Why the average stays near 10 minutes is explained in our piece on hashrate and difficulty.

Why 6 confirmations?

The number traces back to Section 11 of Satoshi Nakamoto's Bitcoin whitepaper. It calculates the odds that an attacker with a share q of the hashrate catches up with the honest chain once the merchant has z confirmations. For an attacker with 10% of the hashrate:

Source: Section 11 table of the whitepaper.

The paper also solves the reverse problem — how many blocks push the risk below 0.1%: 5 blocks against a 10% attacker, 11 against 20%, 24 against 30% and 89 against 40%. The Bitcoin Wiki notes that "6 confirmations" rests on two assumptions — an attacker is unlikely to hold more than 10% of the hashrate, and a sub-0.1% risk is acceptable — and calls both arbitrary. Six blocks is overkill against a casual fraudster and not enough against a well-funded one. For high-value irreversible sales the wiki suggests waiting about 144 blocks, roughly a day.

Note that Bitcoin Core never enforces 6 confirmations. It is a convention, not a network rule.

How many confirmations do you need in practice?

The last row is the only case where the protocol itself fixes a confirmation count. Newly minted coins from a block reward can't be spent until 100 more blocks are built on top. If the miner's block ends up on a losing branch, the reward vanishes — along with any payments already made from it.

What is a UTXO and how bitcoin tracks balances

Bitcoin has no account balances the way a bank or Ethereum does. It has UTXOs — unspent transaction outputs. Each UTXO works like a banknote of a specific value, locked to a spending condition, usually your key. Your wallet balance is simply the sum of your UTXOs (Bitcoin Developer Guide).

A transaction is built in three parts:

1. Inputs point to UTXOs you own (by transaction ID and output index) and carry your signature.
2. Outputs create new UTXOs: one for the recipient and usually one for your change.
3. The fee is not written anywhere explicitly: it is total inputs minus total outputs, and the miner keeps it.

The key property: a UTXO can only be spent in full. If you hold a 0.5 BTC "note" and need to pay 0.1 BTC, the transaction spends the whole 0.5 BTC, sends 0.1 BTC to the seller, returns about 0.4 BTC to you as change on a fresh address, and leaves the difference to the miner. The developer guide puts it plainly: the full value of the UTXOs used must be spent or given to a miner as a fee. Forget the change output and the whole remainder goes to the miner.

Once confirmed, the spent UTXOs drop out of the unspent set and the new ones appear. That set is what nodes check: every input must point to an output that exists and hasn't been spent yet. That is how the network catches double spends. For the kinds of addresses outputs can lock to, see our guide to bitcoin address types.

Why your UTXO count affects the fee

Fees depend on transaction size in virtual bytes (vB), not on the amount, and size grows with every input. According to the Bitcoin Optech size calculator, a native SegWit (P2WPKH) payment with one input and two outputs is about 141 vB, and each extra input of that type adds about 68 vB.

An example at Nov 8, 2026 prices: per our market pulse, BTC traded near $75,976 as of 3:00 AM ET, and mempool.space recommended 3 sat/vB for the next block.

CoinLab calculation: size × fee rate, BTC price on Nov 8, 2026. That's the case for UTXO consolidation: on cheap-fee days like Nov 8, merge many small UTXOs into one by sending them to yourself, so later payments cost less when the network is busy. The trade-off is privacy — consolidation links your addresses and reveals that they share an owner (Bitcoin Optech).

Very small UTXOs can become "dust": under Bitcoin Core policy, nodes by default don't relay outputs below 294 sats for SegWit addresses or below 546 sats for legacy ones, because spending them would cost more than they're worth.

What confirmations looked like on Nov 8, 2026

Take a live run of blocks from mempool.space. Block 975,037 was mined at 2:05 AM ET. A transaction in it reached its sixth confirmation with block 975,042 at 2:42 AM ET — 37 minutes later, faster than the "one hour" rule of thumb. The gaps in between varied widely: block 975,040 arrived 2.6 minutes after its predecessor and held a single transaction (just the miner's reward), while 14.6 minutes passed between blocks 975,041 and 975,042.

Across the current difficulty period the average block time was 10.45 minutes, and the next adjustment, per mempool.space's estimate, would cut difficulty by about 4.2%. At that pace, 6 confirmations take about 63 minutes on average. As of 3:00 AM ET, 61,189 transactions totaling about 13.8 million vB were waiting in the mempool — roughly 14 blocks' worth — but most paid the minimum 1⁠–⁠2 sat/vB, so a payment at 3 sat/vB made the next block.

Limitations: when 6 confirmations aren't a guarantee

• Probability, not finality. Confirmations shrink the chance of reversal but never to zero. Satoshi's math depends on the attacker's hashrate share, and that share changes.
• Pool concentration. On March 23, 2026, a two-block reorg hit height 941,880: the network kept the branch built by Foundry — which, per CryptoSlate, held about 31% of hashrate at the time — and dropped the branch extended by AntPool and ViaBTC. The same piece estimates that against a 30% attacker, six-confirmation reversal risk is about 13%. The reorg was an ordinary block race, not an attack, but it shows the 2008 math assumes a 10% attacker.
• Zero-conf is easy to reverse. While a transaction sits in the mempool it can be replaced by one paying a higher fee (RBF, Bitcoin Optech). For a merchant, "visible" does not mean "paid".
• Confirmations depend on the fee. A payment with a too-low fee rate can wait hours for a block. You can speed it up with RBF or CPFP, where the receiver spends the output with a higher fee.

Common mistakes

1. Accepting a wallet screenshot as proof. Look up the TXID in a block explorer and check the confirmation count.
2. Receiving lots of tiny payments. Each small amount is a separate UTXO you'll later pay to spend as its own input.
3. Confusing confirmations with crediting. An exchange may show the deposit but block withdrawals until its own threshold.
4. Expecting exactly 60 minutes. Block times are random: 6 blocks can take half an hour or an hour and a half.

FAQ

How many confirmations does a bitcoin transaction need? The protocol doesn't require a set number. Six is the common benchmark for meaningful amounts, exchanges set their own (Kraken uses 3), and 0⁠–⁠1 is fine for small purchases.

How long does one confirmation take? About 10 minutes on average — the target block interval. Real intervals are random, from seconds to an hour.

Why is my bitcoin transaction unconfirmed? Usually the fee rate is too low; miners pick higher-paying transactions first. Check the sat/vB rate and bump it with RBF or CPFP. Network load and price are on our Bitcoin page.

What happens to UTXOs after I send? The ones you used are spent for good, and new ones are created for the recipient and for your change. Keep the keys that control them in a cold wallet.

This is not investment advice.