How Long a Bitcoin Transaction Takes
Reviewed and updated September 19, 2026 by the SmartCryptoEarnings editorial team · editorial policy
Bitcoin aims for a new block roughly every ten minutes, and that single number is the source of nearly every wrong expectation. It describes the network's long-run average block interval — not a countdown that starts when you press send.
Your actual wait is decided by several separate stages, only some of which are the blockchain's doing. This page walks through those stages, then shows three worked scenarios so you can see which stage is holding up your own transfer.
- Stage 1Wallet or exchange prepares the transactionA self-custody wallet builds and signs in seconds. A custodial service reviews, queues and often batches withdrawals first.What varies here: Entirely off-chain. With an exchange this stage can dominate the total wait, and no transaction ID exists yet.
- Stage 2Broadcast to the networkThe signed transaction is handed to peer nodes and propagates outward. A transaction ID now exists and can be looked up.What varies here: Usually seconds. It reserves no block space and starts no timer.
- Stage 3Waiting in node mempoolsThe transaction competes against every other unconfirmed transaction for the limited space in upcoming blocks.What varies here: The big one. Your fee rate versus what the queue is currently clearing decides whether this is minutes or much longer.
- Stage 4Included in a blockA miner selects it into a block. This is the first confirmation, and the moment the fee is actually paid.What varies here: Block discovery is a random process around a ten-minute average, so short and long gaps are both normal.
- Stage 5Confirmations accumulateEach subsequent block adds depth. The recipient decides how much depth they require before treating it as settled.What varies here: Recipient policy, not protocol. An exchange may also add its own crediting delay on top.
No stage here has a guaranteed duration. This timeline shows what governs each one so you can identify which stage your own transfer is sitting in.
Broadcast time is not confirmation time
Pressing send in a wallet creates and signs a transaction, then broadcasts it to peers. That part usually takes seconds. Nothing about it reserves a place in a block.
From that moment the transaction sits in node mempools, competing for the next block against every other unconfirmed transaction. Confirmation begins only when a miner includes it — which is a separate event, at a time nobody can schedule.
No page, wallet, explorer or service can guarantee when a specific Bitcoin transaction will confirm. Fee estimates are probabilistic: they describe what has recently been enough, not what will be enough.
The five things that actually set your wait
- Where the transaction started. A self-custody wallet broadcasts immediately. An exchange or custodial service performs its own review, batching and internal queueing first, and that can take far longer than the on-chain part.
- The fee rate you paid, measured in satoshis per virtual byte. Miners select by fee rate, so a transaction priced below what the current queue is clearing waits until the queue thins out.
- Mempool conditions after you broadcast. A fee rate that looked generous can be overtaken minutes later if demand spikes, because you are competing against transactions that had not been created when you sent.
- Block timing variance. Blocks are found by a random search process, so intervals cluster around the ten-minute target rather than matching it. Runs of two-minute and forty-minute gaps are both ordinary.
- What the recipient requires. Many services will not credit a deposit at one confirmation; their own threshold and processing time sit on top of everything above.
Three worked scenarios
These are explanatory walkthroughs of how the stages combine. They are not time estimates, and none of them predicts what your transfer will do.
| Scenario | What happens at each stage | Why the outcome differs |
|---|---|---|
| A — competitive fee rate, ordinary conditions | Wallet broadcasts in seconds; the transaction's fee rate is at or above what recent blocks have been clearing; it is a candidate for the next block template. | Nothing is holding it back except when the next block is found, which is a random interval around the ten-minute average. |
| B — low fee rate during congestion | Broadcast succeeds immediately, but the backlog contains a large volume of higher-paying transactions, so block after block is filled without it. | The transaction is not broken or lost. It waits for the backlog to clear enough that its fee rate becomes competitive, which may be hours or longer, or it may be dropped from node mempools eventually. |
| C — exchange withdrawal | The withdrawal is requested, reviewed and queued internally. Only later does the exchange sign and broadcast a transaction, often batching several customer withdrawals together. | Most of the elapsed time here is off-chain. Until a transaction ID exists, there is nothing on the blockchain to inspect, and fee bumping is not the customer's decision. |
Why the same wait feels different to sender and recipient
- The sender sees the transaction the instant it is broadcast, because their own wallet created it.
- The recipient may see nothing until it appears in their wallet's view of the mempool, or in some wallets not until the first confirmation.
- An exchange recipient adds its own confirmation threshold and its own crediting process after that.
- So 'I sent it an hour ago' and 'I have received nothing' are frequently both true and both accurate descriptions of the same transfer.
What to do while you wait
- Find the transaction ID in the sending wallet or the exchange's withdrawal history. No ID means nothing has been broadcast yet.
- Look the ID up on a Bitcoin block explorer and read the status and the fee rate it paid.
- Compare that fee rate with current network conditions rather than with what felt reasonable when you sent.
- If it is unconfirmed and underpriced, read the stuck-transaction options — replacement or a child transaction may or may not be available to you.
- If it is confirmed but not credited, the remaining delay belongs to the receiving service, not to Bitcoin.
Frequently Asked Questions
How long does a Bitcoin transaction take?
There is no fixed answer. A transaction paying a competitive fee rate during ordinary conditions is typically a candidate for one of the next blocks, and blocks arrive around every ten minutes on average. A transaction paying below the going rate during congestion can remain unconfirmed for hours or longer. Anyone quoting a guaranteed time is describing an average, not your transaction.
Why is my Bitcoin transaction taking so long?
The two common reasons are that the fee rate is too low for current demand, or that the transfer has not been broadcast at all yet because an exchange is still processing it internally. A block explorer tells you which: if there is no transaction ID, nothing has reached the network.
Does sending a larger amount of Bitcoin take longer?
No. Miners select by fee rate per virtual byte, not by the amount transferred. A transaction moving a large amount with a low fee rate waits behind small transactions paying more per byte.
Can I speed up a Bitcoin transaction after sending it?
Sometimes. If you control the sending wallet and it supports fee bumping, replacement may be possible. If you control an output of the transaction, a child transaction paying a higher fee may help. Neither is guaranteed, and custodial withdrawals usually give the customer no such control.
Is one confirmation enough?
That depends entirely on who is receiving. Confirmation requirements are policies set by the recipient or service, not rules of the Bitcoin protocol.
Sources
Spotted something out of date? See our corrections policy and fact-checking policy.
Continue reading
Educational information only. Nothing here is financial, legal or tax advice.