A Bitcoin transaction usually gets its first confirmation in about 10 minutes. The real wait can range from a few minutes to several hours or longer. It depends on network demand, the fee paid and how quickly miners find the next block.
Bitcoin has no central processor. Miners compete to add new blocks, and the network aims for one block every 10 minutes on average. Individual blocks can arrive much sooner or much later than that.
This article collects the main numbers behind Bitcoin confirmation times, fees, exchange deposits and Lightning payments. It also looks at what the data says about stuck transactions.
The figures come from official Bitcoin documentation, fee trackers and exchange support pages. Fee examples use an illustrative Bitcoin price of $100,000 and are not price forecasts.
Key Bitcoin Transaction Statistics at a Glance
| Measure | Figure |
|---|---|
| Target block interval | 10 minutes |
| First confirmation (typical) | About 10 minutes |
| Six confirmations | About 60 minutes |
| Fee for a 150 vB transaction at 2 sat/vB | 300 satoshis |
| Coinbase Lightning processing fee | 0.2% |
| Default mempool expiry in Bitcoin Core | 336 hours (14 days) |
Each of these numbers is explained in the sections below. Every section includes a chart that shows the figures side by side.
Bitcoin Confirmation Time Statistics
Bitcoin transaction times depend on how many confirmations are needed and whether the payment is included in the next available block. A confirmation means the transaction has been recorded in a block on the blockchain.
When a payment is first sent, it is broadcast to the network in seconds. At that point it has zero confirmations. It becomes part of the accepted history only after a miner adds a block that contains it.
| Transaction status | Estimated time | What it means |
|---|---|---|
| Transaction broadcast | Usually seconds | Payment has been submitted to the network |
| 0 confirmations | Immediate | Visible but not yet in a block |
| 1 confirmation | About 10 minutes | Included in a block |
| 2 confirmations | About 20 minutes | Another block has been added |
| 3 confirmations | About 30 minutes | More protection against reversal |
| 6 confirmations | About 60 minutes | Common benchmark for high-value settlement |
| Lightning Network payment | Usually seconds | Settles through supported Lightning channels |
These estimates assume a competitive fee and normal block production. A transaction that pays too little may stay unconfirmed for hours or days before the confirmation process even begins.
According to Bitcoin.org, blocks are produced about every 10 minutes on average. There is no guaranteed maximum waiting time. Block discovery is random, so one block might arrive after one minute and the next after 30 minutes or more.
How Many Confirmations Are Enough?
The right number depends on the value of the payment and how much risk the receiver will accept. For a small personal payment, one confirmation may be enough. Exchanges and businesses often ask for several.
Six confirmations is the benchmark named in Bitcoin’s developer documentation for substantial payments. It does not mean a transaction becomes impossible to reverse after exactly six blocks.
Bitcoin has what is called probabilistic finality. The risk of reversal falls as more proof-of-work builds on top of the transaction. Accepting an unconfirmed payment carries a higher risk of double spending than waiting for a block.
Why Block Times Vary
The 10-minute figure is a target, not a timer. Miners find blocks through a random process, so the gap between blocks changes from one block to the next. Some arrive within a minute, while others take half an hour.
This is why a payment with a good fee can still feel slow. The wait for the next block is the same for every transaction, no matter how much it pays.
Bitcoin Transaction Fee Statistics
Bitcoin fees are not a percentage of the amount sent. They are based on the size of the transaction data and the fee rate the sender picks. Size is measured in virtual bytes (vB), and the rate is measured in satoshis per virtual byte (sat/vB).
The formula is simple: fee = transaction size (vB) multiplied by fee rate (sat/vB). One satoshi equals 0.00000001 BTC.
The table below uses a hypothetical 150 vB transaction. The dollar column uses an illustrative Bitcoin price of $100,000.
| Fee rate | Total fee | Cost at $100,000 per BTC |
|---|---|---|
| 1 sat/vB | 150 satoshis | $0.15 |
| 2 sat/vB | 300 satoshis | $0.30 |
| 5 sat/vB | 750 satoshis | $0.75 |
| 10 sat/vB | 1,500 satoshis | $1.50 |
| 20 sat/vB | 3,000 satoshis | $3.00 |
| 50 sat/vB | 7,500 satoshis | $7.50 |
These are worked examples, not live quotes. Real transaction sizes and required fee rates vary from one payment to the next.
As of 28 October 2026, the Mempool Project showed suggested fee rates of around 1 to 2 sat/vB during the research check. That points to low network costs at the time, but fee suggestions can change within minutes.
Does Sending More Bitcoin Raise the Fee?
Not by itself. Sending $100 of Bitcoin can cost about the same as sending $100,000 if the two transactions have a similar structure. The network charges for data, not for value.
Structure does matter. A wallet filled with many small payments may need to combine several unspent outputs (UTXOs) to make one larger transfer. A payment with five inputs is bigger in data terms than one with a single input, so it costs more.
Address format plays a part too. SegWit and Taproot transactions benefit from Bitcoin’s witness-data discount, although the actual savings depend on how each transaction is built.
How Users Can Lower Fees
The simplest step is to avoid paying for high-priority confirmation when a transfer is not urgent. Checking current fee estimates before sending can also prevent overpayment.
Wallets that support SegWit or Taproot may be more efficient than older address formats. Combining small UTXOs when fees are low can reduce the cost of later transactions, although the combining step is itself an on-chain transaction and can affect privacy.
Fee Rate and Delay Statistics
Most delays come down to three things: a fee that is too low, a busy network and the random timing of blocks. Exchange rules can add a fourth.
Miners generally favor transactions that pay more per unit of block space. If a transaction offers a lower fee rate than its competitors, miners may keep choosing other payments first.
The source material gives a clear example. A transaction paying 2 sat/vB may sit in the queue while most competing payments pay 20 sat/vB. It could confirm later if demand drops, but no timeframe is guaranteed.
For a 150 vB transaction, that gap is 300 satoshis against 3,000 satoshis. The competing fee is ten times higher.
Why Congestion Changes the Numbers
Bitcoin has limited block space. When more people send transactions, more payments compete for the same room. Heavy trading activity, speculative interest and other blockchain use can all push demand up.
Higher demand can raise the fee rate needed for quick inclusion. A fee that looked competitive when a payment was sent can become too low if demand rises afterward.
A Fee Does Not Remove Block Timing
Even a payment with a high fee has to wait for a miner to find a block. Bitcoin targets a 10-minute average, but a block might take 30 minutes or longer. A higher fee improves the chance of quick inclusion, but it cannot promise confirmation within 10 minutes.
| Fee category | General purpose |
|---|---|
| High priority | Target inclusion in an upcoming block |
| Medium priority | Balance cost and speed |
| Low priority | Accept a longer possible wait |
| No priority | Keep fees as low as possible when timing does not matter |
Fee tools such as mempool.space show suggested rates for each urgency level. These are predictions, not guarantees.
Exchange Deposit Statistics
Moving Bitcoin between exchanges adds steps. The sending exchange may need to process the withdrawal before it broadcasts the transaction. The receiving exchange must then see the payment and wait for its required number of confirmations.
Coinbase Exchange documentation gives an example that requires two Bitcoin network confirmations before a deposit is complete. At the average block interval, that is about 20 minutes after prompt inclusion. Requirements can differ between Coinbase products and may change.
Kraken’s October 2026 documentation describes three confirmations for ordinary Bitcoin deposits. That points to about 30 minutes under normal block production, assuming the transaction confirms quickly.
| Platform | Confirmations required | Approximate time at 10 minutes per block |
|---|---|---|
| Coinbase Exchange (example) | 2 | About 20 minutes |
| Kraken (ordinary deposit) | 3 | About 30 minutes |
| High-value benchmark | 6 | About 60 minutes |
Neither exchange controls when miners find blocks. Account limits or security reviews can stretch the process further.
Confirmed on the Network, Pending on the Exchange
A transfer can be confirmed on the blockchain and still not appear in an exchange account. Centralized exchanges may run withdrawal reviews, security checks or their own confirmation rules. These delays are separate from Bitcoin’s processing time.
Some exchanges also offer internal transfers between customers. These may not use an ordinary Bitcoin transaction, so they can appear almost at once and may avoid network fees. They depend on the exchange’s own custody and accounting records rather than independent blockchain settlement.
Lightning Network Statistics
The Lightning Network is a payment layer built on top of Bitcoin. Instead of recording each payment on the main blockchain, it sends payments through connected channels. A successful Lightning payment can settle within seconds.
That speed suits everyday purchases, small payments and frequent transfers. Both sides need compatible wallets or services, and the payment needs enough liquidity and a working route. Larger payments can fail if no suitable route is found.
Opening or closing a channel can involve on-chain Bitcoin fees. Those costs are easy to miss when comparing Lightning with regular transfers.
Are Lightning Payments Cheaper?
They often are, but the cost depends on the provider. Some Lightning wallets charge very small routing fees. Others add processing charges.
Coinbase’s published pricing disclosure lists a 0.2% processing fee for sending Bitcoin through Lightning. On a $1,000 transfer, that is $2.
| Method | Cost on the example transfer |
|---|---|
| Lightning via Coinbase (0.2% on $1,000) | $2.00 |
| On-chain, 1 sat/vB (150 vB) | $0.15 |
| On-chain, 2 sat/vB (150 vB) | $0.30 |
| On-chain, 5 sat/vB (150 vB) | $0.75 |
| On-chain, 10 sat/vB (150 vB) | $1.50 |
| On-chain, 20 sat/vB (150 vB) | $3.00 |
The comparison shows that a direct Bitcoin transaction can cost less when on-chain fees are low. At 20 sat/vB, the on-chain fee is higher than the Lightning fee in this example. Lightning is best judged on both speed and total cost.
Stuck Transaction Statistics
A Bitcoin transaction can stay pending when miners keep choosing payments with higher fees. Low-fee transactions can remain unconfirmed for 24 hours or longer. That does not mean the Bitcoin has disappeared.
If a transaction is unconfirmed, the funds have not been permanently moved on the blockchain. The pending payment can stay visible across network nodes for a long time.
How Long Can a Transaction Stay Pending?
Bitcoin Core’s default mempool expiry period is 336 hours, which equals 14 days. A node can drop an unconfirmed transaction after that time, or sooner if its memory fills up.
Expiry is not a network-wide cancellation. Other nodes may still hold the transaction, and someone could rebroadcast it. Users should check their wallet status before assuming a transaction is gone.
Ways to Move a Stuck Payment
| Option | How it works | Limits |
|---|---|---|
| Wait | Lets higher-fee payments clear first | No fixed time for confirmation |
| Replace-by-Fee (RBF) | Replaces the payment with one that pays a higher fee | Needs wallet support and enough fee |
| Child-Pays-for-Parent (CPFP) | Spends an output of the pending payment with a high-fee transaction | Not every wallet supports it |
| Contact the exchange | The platform may control the fee settings | Use official support only |
Bitcoin Core has supported full-RBF relay by default since version 28.0, although wallet screens and network policies differ. A replacement must meet the relevant fee and relay rules.
With CPFP, miners can weigh the combined fees of both transactions and include them together. It helps most when the receiver controls an output from the pending payment.
Can a Bitcoin Transaction Be Reversed?
A confirmed Bitcoin transaction cannot normally be canceled through a wallet or exchange. Bitcoin has no chargeback system. An unconfirmed payment can sometimes be replaced, but only before the original confirms.
Once a transaction has built up confirmations, reversing it would take a blockchain reorganization or another exceptional step. A transfer to a wrong address can mean permanent loss, so checking the address matters.
How to Track a Pending Payment
Every transaction has a unique ID, often called a TXID or transaction hash. Most wallets and exchanges show it in the transaction details.
Entering the TXID in a blockchain explorer shows the confirmation status, fee rate, amount and addresses. It may also estimate when an unconfirmed payment could be included in a block. Zero confirmations means the payment is still waiting, not that it has failed.
Why Pending Is Not the Same as Lost
A payment that has not confirmed is still waiting in the queue. The sender still controls the funds until a block includes the transaction. This is different from sending Bitcoin to the wrong address, which can cause permanent loss once confirmed.
Telling the two cases apart matters. A delayed payment can often be fixed with a higher fee, while a mistaken transfer usually cannot be undone.
What the Bitcoin Transaction Time Numbers Show
Bitcoin transactions typically get a first confirmation in around 10 minutes, and six confirmations take about one hour under normal conditions. These are averages, not promises.
Actual times depend on congestion, fees, block production and the rules of the receiving service. A low-fee payment can take hours or days, while a competitive fee improves the chance of inclusion in an upcoming block.
The statistics also show how small on-chain fees can be. A 150 vB transaction costs $0.30 at 2 sat/vB and $3.00 at 20 sat/vB in the examples above. Fees depend on data size and fee rate, not on the amount sent.
For people moving Bitcoin between wallets, checking current fee estimates is the simplest way to balance cost and speed. Those making frequent small payments may find Lightning useful if their wallets and receiving services support it.
The key distinction is between a transaction being broadcast, confirmed on the blockchain and credited by a receiving platform. Verify the recipient address, check network conditions, choose a suitable fee and allow time for the confirmations required.
Sources
- Bitcoin.org: Bitcoin Frequently Asked Questions
- Bitcoin Developer Documentation: Payment Processing and Confirmations
- Bitcoin Developer Documentation: Bitcoin Transactions and UTXOs
- Mempool Project: Bitcoin Network Fees and Transaction Explorer
- Mempool Project: Transaction Fee and Confirmation FAQ
- Blockstream: Why Bitcoin Has Transaction Fees
- Blockstream: Replace-by-Fee Explained
- Bitcoin Design Foundation: Bitcoin and Lightning Transactions
- Lightning Labs: Lightning Network Payment Routing
- Coinbase: Pending Cryptocurrency Deposits
- Coinbase: Cryptocurrency Pricing and Fee Disclosures
- Kraken: Cryptocurrency Deposit Processing Times
- Bitcoin.org: Important Bitcoin Security Information
Disclaimer: This article is for educational purposes only. Bitcoin transaction fees and confirmation times change with network conditions. Examples and estimated processing times are not guarantees. Always verify live fees, receiving addresses and platform requirements before transferring cryptocurrency.
