What is a transaction confirmation?
A confirmation means the transaction has been included in a block and the network has accepted it into its history. Until that happens, the transfer is in a waiting queue and could theoretically be replaced or dropped.
First the sender signs the transaction and broadcasts it to the network. A miner or validator picks it from the queue and includes it in a block: that is the first confirmation. Each subsequent block on top adds another one. The more blocks cover your transaction, the harder it is to reverse, which is why payment recipients wait for a certain number of confirmations.
How long does confirmation take on Bitcoin, Ethereum, Tron and other networks?
From a few seconds on Solana and Tron to tens of minutes on Bitcoin. Below are benchmarks for block speed.
- Bitcoin. A block roughly every ten minutes, so one confirmation takes about ten minutes and is sometimes noticeably longer.
- Litecoin. Blocks come out about every two and a half minutes.
- Ethereum. A block approximately every twelve seconds.
- Tron and BNB Smart Chain. A block in a few seconds, so confirmation usually takes from seconds to a couple of minutes.
- Solana. Blocks come in under a second, and confirmation takes seconds.
These are benchmarks, not guarantees: network load changes the actual time. This is especially noticeable on Bitcoin and Ethereum.
Why is the average block time not the same as your wait?
The average block time describes the network as a whole, not your transaction. Bitcoin blocks arrive randomly: sometimes two in a row within a couple of minutes, sometimes you have to wait half an hour for the next one. So "ten minutes on average" does not mean "exactly ten".
There is a second reason. Your transaction may not make it into the nearest block even if it has already been found: space in a block is limited, and miners take transactions with higher fees first.
The practical takeaway: allow some margin. If one confirmation on Bitcoin usually takes ten minutes, plan for up to an hour and do not panic early.
What does confirmation speed depend on?
The main factors are the fee amount, network load and the required number of confirmations.
- Network fee. Transactions with a low fee wait longer in the queue. More on network and service fees: exchange fees.
- Network load. During periods of heavy activity the queue is longer, and a fee that was enough yesterday may be low today.
- Required number of confirmations. For large amounts the receiving side may wait for more blocks.
- Type of operation. Token transfers and smart contract calls are processed differently on some networks than simple transfers of the base coin.
How many confirmations are needed for an exchange?
There is no single number: it depends on the network, the amount and the receiving side's rules. As a rule, fast networks need only a small number of blocks, and for Bitcoin people usually wait for one to several.
The logic is simple. The larger the payment and the higher the chance of history being rolled back, the more confirmations it makes sense to require. For an exchange service it is a matter of protection against double spending; for you it is simply the reason the payout does not start right after you send.
You do not need to guess the specific number of confirmations for your order: follow the order status and check the txid in an explorer.
How does confirmation time affect how long an exchange takes?
Almost all of the exchange time is confirmation of your payment. Once the network has confirmed the payment, the exchange itself goes quickly.
At BITWHITE the rate, the fee and the final amount are visible before you create the order, and the rate is fixed at the moment the order is created. The payment address for each order is valid for up to two hours. This means slow confirmation does not by itself change the rate, but you must send the payment within the deadline. A payment that arrives after the deadline goes to an operator for manual review.
If you need maximum speed, choose a fast network for sending. For stablecoins, the differences between networks are covered in the article USDT networks: TRC20, ERC20, BEP20. The overall order process is described in the guide how to exchange crypto.
What should you do if a transaction is not confirming?
First of all, do not send the payment again. A repeat leads to a double payment, not to the first transaction being sped up.
- Find the transaction by its txid (transaction hash) in a blockchain explorer. How to do it: txid and blockchain explorer.
- If the status is "pending", the transaction is in the queue: wait, especially if the fee is low.
- If the status is "success" but the order is not moving, compare the recipient address and amount with the order details.
- If the transaction is not in the explorer at all, check that the right network is selected and that the wallet actually sent the transfer.
- If a long time has passed, write to support on Telegram and attach your order number (BW-…) and txid.
Can you speed up a stuck transaction?
Sometimes you can, but the method depends on the network and the wallet. There is generally no cancellation, only replacement or acceleration.
- Bitcoin. Some wallets can replace an unconfirmed transaction with a version that has a higher fee, or create a child transaction that incentivizes miners.
- Ethereum and compatible networks. You can replace a transaction with a new one that has the same sequence number (nonce) and a higher fee. Otherwise subsequent operations will queue behind it.
- Fast networks. On Tron and Solana, hangs are rare: a transaction either goes through in seconds or is rejected.
If your wallet has no such feature, all that is left is to wait. Before changing anything, check the status in the explorer and make sure the operation has not been confirmed.
Which mistakes most often cause delays?
Most delays are caused not by the network but by the sender's actions.
- A fee that is too low. The wallet offers an "economy" option, and the transaction gets stuck in the queue.
- Sending again. A payment that seemed lost is sent anew and paid for twice.
- The wrong network. Coins went out on a network different from the one in the order. Such payments go to manual review, and the result is not guaranteed.
- The wrong amount. An underpayment or overpayment is also passed to an operator; details are in the article underpayment and overpayment.
- An expired address. Sending after the order deadline has passed.
Example: how time is distributed in a Bitcoin exchange
Consider a hypothetical situation. You create an order to exchange Bitcoin, and at 12:00 you send the payment from your wallet. A block is found at 12:07, and the transaction gets its first confirmation. The next block appears only at 12:31: for a requirement of two confirmations, that is already half an hour.
If you had sent the payment with a minimal fee during a busy period, it might not have made it into the first blocks at all and would wait longer. And with a USDT transfer on a fast network, the same process would take minutes.
The takeaway: variation in time on Bitcoin is normal, and a wait of twenty to thirty minutes is no reason to think something is broken.
How does "in a block" differ from "finally confirmed"?
Inclusion in a block and the finality of a payment are not the same thing. After the first confirmation the transaction is already visible on the network, but the probability that the block will be replaced by another version of the chain is not yet zero. With each new block it drops quickly.
So in the explorer you may see the transaction as successful while the receiving service is still waiting for additional blocks. This is ordinary caution, not a failure. Individual networks use their own finalization mechanisms, but in practice one thing matters: the "success" status in the explorer and the start of the payout may not coincide in time.
If you are sure the address and amount are correct, patience usually solves the problem without any extra action.
How do you choose a network if speed matters?
If a coin exists on several networks, the fastest one with the lowest fee is usually the best fit, provided it is supported by both the sender and the recipient. For stablecoins, the choice of network changes both the time and the cost of the transfer.
But speed is not the main criterion. Before sending, make sure the source wallet can actually work with the chosen network and that the receiving address was created on the same network. A mixed-up network costs more than any wait. It is convenient to check addresses using the recommendations in the article how to check a wallet address.
Checklist: what to check while you wait for confirmation
- Save the order number and the txid of your transfer.
- Open the txid in the explorer for the network you sent on.
- Make sure the recipient address and amount match the order details.
- Check the status: pending means waiting, success means included in a block.
- Do not send the payment again and do not create a second order "just in case".
- Make sure you are on the official domain bitwhite.net. Signs of fakes: how to spot a fake exchange service.
- If the status does not change for too long, contact support on Telegram with your order number and txid.
The service never asks for a seed phrase under any circumstances, including because of a "stuck" payment.