Bitcoin confirmations: why a BTC transfer takes time
What confirmations are, how many an exchanger waits for, and how to speed up a stuck transaction.
You sent Bitcoin, your wallet says “Sent”, but the swap service or exchange still shows “Waiting for confirmations”. Ten minutes pass, twenty, sometimes an hour. To a newcomer this looks like a glitch or a delay on the service’s side, but it’s simply how the Bitcoin network works: a transfer becomes reliable not when it’s sent but as new blocks appear.
In this article we explain what confirmations are, why you have to wait for them, how many are needed in different situations, why a transaction can get “stuck” for hours and how to speed it up — plus how to choose the right fee so your transfer goes through quickly without overpaying.
A Bitcoin transfer’s journey: from the button to the block
To see where the waiting comes from, it helps to follow what happens to a transfer after you press “Send”.
- Signing. The wallet builds the transaction — which coins are spent, where and how much is sent, what the fee is — and signs it with your private key.
- Broadcast. The signed transaction is sent to Bitcoin network nodes. Within seconds, thousands of nodes worldwide know about it.
- Mempool. Each node puts the transaction into its mempool — the queue of unconfirmed transactions. At this point the recipient can already see the transfer as “unconfirmed”.
- Inclusion in a block. Miners gather transactions from the mempool into a candidate block and search for its solution. Whoever finds it first publishes the block, and your transaction gets its first confirmation.
- More confirmations. Each subsequent block built on top adds another confirmation.
The wait consists of two parts: how long the transaction sat in the mempool before getting into a block, and how many blocks the recipient required after that.
What a confirmation is and why to wait for it
The number of confirmations is the number of blocks in the chain counting from the block that contains your transaction. One confirmation means the transaction is in the latest block. Six confirmations mean five more blocks have been built on top of its block.
Confirmations matter because the latest block can theoretically be replaced. Occasionally two miners find blocks almost simultaneously, and for a while the network sees two versions of the chain. Eventually the one that grows faster wins, and transactions from the “losing” block return to the mempool. This is rare and usually affects only the single latest block.
The main reason, though, is protection against double spending. While a transaction is unconfirmed, the sender can technically try to replace it with another one that sends the same coins elsewhere. With each new block, rewriting history becomes exponentially harder and more expensive, so several confirmations make a transfer practically irreversible.
How many confirmations are needed
There is no single rule: each service decides how many confirmations to wait for based on the amount and its appetite for risk. Rough guidelines:
| Situation | Confirmations | Approximate time |
|---|---|---|
| A small amount between people who know each other | 0–1 | Immediately or about 10 minutes |
| Swap services and exchanges, typical amounts | 1–3 | 10–30 minutes |
| Large amounts | 3–6 | 30–60 minutes |
| The classic “irreversibility” standard | 6 | About an hour |
These times assume the transaction made it into the next block straight away. If the fee was low and the transaction waited in the mempool, add that queueing time.
The mempool and fees: why a transaction gets “stuck”
Block space is limited, and sometimes more people want to send transfers than the next blocks can hold. So the network has a fee market: miners include the transactions that pay the most per unit of size first. This rate is measured in satoshis per virtual byte (sat/vB).
It’s important to understand that the Bitcoin fee depends not on the amount sent but on the transaction’s size in bytes and current network load. A transfer of 0.001 BTC and one of 100 BTC can cost the same if the transactions are the same size.
If you send a transaction with a low rate while the network is busy, it waits until higher-paying transactions are cleared. That can take hours, and during peaks, days. If a transaction stays unconfirmed for too long, nodes eventually drop it from the mempool (by default after two weeks on many nodes), and the coins become available to the sender again.
| Fee priority | When to choose it | What to expect |
|---|---|---|
| High | Paying an order with a timer, an urgent transfer | Inclusion in the next block or the one after |
| Medium | A regular transfer without a strict deadline | Usually within an hour |
| Low | Moving funds between your own wallets, consolidation | From a few hours to a day or longer |
How to choose the right fee
Most wallets offer presets: “fast”, “normal”, “economy”. They are calculated from the current state of the mempool and generally work well. If you want to choose deliberately, check the recommendations on mempool.space — it shows what rate you need to get into the next blocks.
How to speed up a stuck transaction
If a transaction is already stuck in the mempool, there are several ways to speed it up.
RBF (Replace-by-Fee)
RBF lets you broadcast a new version of the same transaction with a higher fee. Nodes and miners replace the old version with the new one, and it gets into a block faster. Many modern wallets support RBF: an unconfirmed transaction’s details show a “Speed up” or “Bump fee” button. The recipient doesn’t need to do anything — the address and amount stay the same.
CPFP (Child-Pays-for-Parent)
CPFP works from the recipient’s side (or the sender’s, if the transaction has change). A new transaction is created that spends the still-unconfirmed coins and pays a high fee. To collect that fee, a miner must include both transactions — the “parent” and the “child” — in a block. The high fee effectively pulls the stuck transaction along.
Accelerators and waiting
There are paid accelerator services that arrange with mining pools to include a transaction. And if the transfer isn’t urgent, you can simply wait: network load comes in waves, and during quiet hours the queue clears quickly.
Confirmations on other networks
The word “confirmations” isn’t unique to Bitcoin, but on different networks it means very different waiting times. On fast blockchains, blocks are produced every few seconds, so services wait for more blocks, yet crediting still takes less time overall. Guidelines for popular networks:
| Network | Block time (average) | Typically required | Total until credited |
|---|---|---|---|
| Bitcoin | 10 minutes | 1–3 confirmations | 10–30 minutes |
| Litecoin | 2.5 minutes | several confirmations | 5–15 minutes |
| Ethereum | 12 seconds | dozens of blocks | a few minutes |
| TRON | 3 seconds | about 20 blocks | about a minute |
| TON | a few seconds | block finalisation | seconds |
How services choose the number of confirmations
The number of confirmations is a trade-off between speed and risk. The larger the amount, the more an attacker stands to gain from a double-spend attempt, and the more blocks it makes sense to wait for. That’s why many services use a tiered scheme: one confirmation is enough for small amounts, two or three for medium ones, and very large transfers wait for up to six.
Besides the amount, network conditions matter. If Bitcoin is going through a wave of heavy load or there have been block replacements, a service may temporarily raise its requirements. The flip side is that customers wait longer, so honest services state in advance how many confirmations are needed and show the progress on the order page.
Why a swap service won’t pay out on an unconfirmed transfer
Customers sometimes ask: “The transfer is visible in the explorer, so why aren’t you paying out?” The thing is, an unconfirmed transaction is still only an intention. Until it’s in a block, it can be replaced by another one, and if the fee is too low it can drop out of the mempool altogether. If a service paid out on such a transfer and the original transaction were replaced, the service would lose money.
So waiting for confirmations isn’t a formality or red tape — it’s basic protection that lets a swap service work honestly and reliably for all customers.
How it works at ROVEN exchange
At ROVEN exchange the rate is locked when the order is created, so a drop in the BTC price while your transaction waits for confirmations won’t reduce the amount you receive. An operator tracks the transfer on the blockchain and starts the payout after the required number of confirmations, and the order status updates on the site and in Telegram.
If you sent BTC on time but, due to network congestion, the confirmations arrived after the order timer ran out, contact support with the transaction hash. The operator will see when it was sent and help complete the swap.
How to check the status of a BTC transfer
The most convenient way is the mempool.space explorer. Paste the transaction hash (TXID) or an address into the search, and you’ll see:
- Status — “Unconfirmed” (in the mempool) or the number of confirmations.
- Fee rate in sat/vB and how it compares with current recommended rates.
- Estimated time to inclusion in a block given the current queue.
- RBF flag — whether this transaction’s fee can be bumped.
- Recipients and amounts, including change returned to your address.
If you’re paying a swap order, save the hash and pass it to the operator if needed — the transfer will be found faster.
Frequently asked questions
Why does a BTC transfer take longer than USDT on TRON?
Bitcoin produces a block every 10 minutes on average, TRON every few seconds. On top of that, services usually wait for several Bitcoin confirmations. It’s the price of the network’s maximum reliability and decentralisation.
Can an unconfirmed transaction be cancelled?
Not directly, but if your wallet supports RBF, you can replace the transaction with a new one at a higher fee that sends the coins back to your own address. This only works if the original transaction hasn’t been included in a block yet.
What happens if the transaction never confirms?
Eventually nodes drop it from the mempool, and the coins become available in your wallet again. You can then resend the transfer with a normal fee.
Does the amount affect the speed?
No. Speed depends on the fee rate in sat/vB, not the amount. A large transfer with a low rate will wait longer than a small one with a high rate.
