Bitcoin Transaction Fees And Confirmations: Why Payments Wait
Bitcoin fees depend on transaction size and demand for block space. Confirmations explain why seeing a payment is different from settling it.

You send Bitcoin (BTC), your wallet says it has gone through, and the receiver still sees “pending”. Has the payment failed?
Not necessarily. A transaction can reach the network before it enters Bitcoin's shared transaction record, the blockchain. Being visible and being confirmed are different stages of a payment. The fee helps determine how competitive the transaction is for inclusion in a block, a batch of transactions added to that record.
What does a Bitcoin transaction fee pay for?
The network fee goes to the miner who includes the transaction in a block. It buys space for the transaction's data, rather than charging a percentage of the money sent. Bitcoin.org's fee guide explains why demand for that limited space makes fees change.
Imagine two payments with the same data size. One moves a small amount of bitcoin; the other moves much more. At the same fee rate, their network fees can be identical. Sending more money does not, by itself, make a transaction larger.
The detail that matters is how the payment is put together. Bitcoin spends pieces of value received in earlier transactions. These are called inputs when your wallet uses them in a new payment. The payment creates outputs, which specify where the value can be spent next. The developer guide explains this structure.
Combining several earlier receipts into one payment means including more inputs. That adds data even if the amount you send is small.
An exchange's withdrawal charge can differ from the actual network fee. Coinbase Exchange explains that it charges an estimate of network fees, which can differ from what it ultimately pays because of changing congestion or batching, combining several withdrawals into one transaction.
What does sat/vB mean?
Wallets commonly quote the fee rate in satoshis per virtual byte, written sat/vB. A satoshi, or sat, is one hundred-millionth of a bitcoin. A virtual byte measures the transaction's size for fee calculations.
More precisely, virtual size comes from transaction weight, a measure that accounts differently for different parts of the transaction data. Bitcoin's SegWit specification defines virtual size as weight divided by four, rounded up. It is a data measurement, not the value being transferred.
Here is a hypothetical calculation. A transaction of 140 vB at 10 sat/vB pays:
140 × 10 = 1,400 sats, or 0.000014 BTC.
Neither the size nor the rate is a quote for your payment. The wallet's actual transaction may be a different size, and its suggested rate can change before you send.
Why is a Bitcoin payment still pending?
Before confirmation, a transaction may sit in a node's mempool, its collection of unconfirmed transactions. A node is a computer running Bitcoin software. This is not one global queue with a numbered place: individual nodes maintain their own view of waiting transactions, as the developer guide describes.
When demand rises, a fee rate that previously looked competitive may fall behind newer transactions. A wallet's “fast” option is an estimate of what could confirm within a target number of blocks. Fee estimation is a probability assessment, not a reservation in the next block.
That explains why the same payment can take longer than the wallet first suggested. A higher fee can improve its competitiveness, but cannot make miners find the next block on demand.
How long do Bitcoin confirmations take?
Bitcoin aims for an average interval of about ten minutes between blocks. That is not a ten-minute delivery promise. A particular block can arrive much sooner or later, and your transaction may miss several blocks before its first inclusion.
The block containing your transaction gives it one confirmation. Each further block built on top increases that count. More confirmations make it harder to replace the transaction by rewriting recent blockchain history. Our explainer on what Bitcoin miners do covers how blocks are produced.
You may hear that a payment needs six confirmations. That is a convention, rather than a rule every receiver must use. The developer guide's confirmation discussion connects the decision to the value at risk and the receiver's tolerance for a reversal.
An exchange crediting your account is another step. For example, Coinbase Exchange says deposits remain pending until its required network confirmations arrive, and that its own node synchronisation can also cause delays. A confirmation on Bitcoin and an available exchange balance are therefore different things to check.

Can a waiting transaction be sped up?
Some wallets offer a fee bump. Replace-by-fee, or RBF, replaces an unconfirmed transaction with another that shares an input and offers a higher fee. Whether you can use it depends on your wallet and the applicable network relay rules, the rules nodes use when passing transactions along.
Another method is child pays for parent, or CPFP. Someone able to spend an output of the waiting transaction creates a new transaction with a higher fee. Miners can then have an incentive to include both together. It needs a suitable spendable output and wallet support; it is not an option for every pending payment.
Both methods cost extra and still depend on a miner including the transactions. Their purpose is to improve the fee offer, not guarantee a deadline.
How can Lightning payments be faster?
The Lightning Network is a payment system built on Bitcoin that uses channels, arrangements holding bitcoin while participants update their balances. Payments through these channels do not each need a new Bitcoin block. Lightning Labs' merchant guide explains how this enables fast payments, while also requiring enough available funds along a payment route.
That introduces different constraints. A payment can fail when no suitable route has enough capacity. Opening and closing channels involves Bitcoin transactions, and some channel closures can leave funds temporarily unavailable. Lightning Labs describes these channel and liquidity trade-offs: a quick channel payment and a confirmed transaction on Bitcoin's blockchain follow different processes.
Which part of the payment is waiting?
For a payment on Bitcoin's blockchain, the transaction's confirmation count identifies the stage. Zero means it has not yet entered a block. If it is confirmed but an exchange still shows a pending balance, the remaining wait may involve that platform's confirmation requirement or processing. Those are different delays, even when the wallet gives both the same label.
Filed underCrypto · Bitcoin · Payments
How our stories are produced:Editorial policy


