Stuck Transaction: What to Do If Your Transfer Is Not Confirming

What “a stuck transaction” means

A cryptocurrency transfer does not reach the recipient instantly. First you sign the transaction in your wallet, then it enters the network and waits for a miner or validator to include it in a block. Only after that does the transfer get its first confirmation. If noticeably more time passes between sending and inclusion in a block than you expected, users say the transaction is “stuck”.

The main thing to understand is that in most cases the money has not disappeared. Until the transaction is confirmed, the funds are either not yet finally debited or are sitting in the network queue. A blockchain does not lose transfers, it just processes them in order of priority. How confirmations work in different networks is covered in the article how long to wait for confirmations.

Why a transaction gets stuck

There are usually several causes, and they often occur together.

• Low fee. Miners and validators take transactions with higher fees first. If you set the minimum, the transfer may sit in the queue for a long time.
• Network congestion. When many people want to send funds, the queue grows and the fees needed for fast inclusion in a block rise.
• Large transaction size. In the Bitcoin network, transaction size depends on the number of inputs. A transfer assembled from many small receipts takes up more space and needs a larger total fee.
• Wallet or node problems. Sometimes a wallet uses an overloaded server and shows an outdated status although everything is fine in the network.
• Dependence on another transaction. If your transfer spends funds from a transaction that is not yet confirmed, it will not be confirmed before that one.

We covered the difference between the service fee and the network fee in the article on exchange fees: the network fee goes to the network, not to the service, and it is what determines how fast the transfer is included in a block.

What the mempool is and how it relates to the queue

The mempool, or pool of unconfirmed transactions, is where a transaction waits to be included in a block. Every node in the network has its own mempool, but they are broadly similar. While your transfer is there, it is visible in the explorer with the status “unconfirmed” or “pending”.

If the fee is too low, nodes may eventually drop the transaction from their mempool. Then the explorer may stop showing it, and the wallet will return the funds to the available balance. This does not mean the money has disappeared: the network simply no longer has that transaction waiting for confirmation. How long this takes depends on the network and node settings, so do not count on a specific number of hours.

How to check a transaction by txid

A txid, or transaction hash, is a unique identifier of your transfer. You can find it in your wallet history or in the email from the exchange you sent the funds from. Anyone can use it to see the state of the transfer. A detailed overview is in the article about the txid and the blockchain explorer.

1. Copy the txid from your wallet. Do not type it manually.
2. Open a blockchain explorer for the relevant network: Bitcoin, Ethereum, Tron and other networks each have their own.
3. Paste the txid into the search bar.
4. Look at the status: unconfirmed, in a block, number of confirmations.
5. Compare the recipient address, amount and network with what you intended to send.

If the explorer does not find the transaction, check that the correct network is selected and wait a few minutes: data sometimes appears with a delay. If there is still nothing after that, the wallet may never have broadcast the transaction to the network.

How to tell a stuck transaction from ordinary waiting

Not every wait is a stuck transaction. Confirmation time depends on the network. In Bitcoin, blocks appear about once every ten minutes, and several confirmations take noticeable time. In other networks blocks come faster, but the number of required confirmations also differs. These are guidelines, not guarantees, and in busy periods the times stretch.

Look at three signs:

• The transaction is visible in the explorer with the status “pending”. This is a normal queue, and the only question is the fee.
• The transaction is already in a block, but has fewer confirmations than the recipient requires. You need to wait for the next blocks.
• The transaction is not in the explorer at all. Then the problem is most likely with the wallet or the sending, not with the network queue.

If you are in the first or second case, this is ordinary waiting. Only the third requires looking into the wallet.

When it is enough to simply wait

Waiting is reasonable if the transaction is visible in the explorer, the address and amount are correct, and the network is currently busy. A low fee does not make a transfer invalid. It will be processed when the queue clears, for example in periods of lower activity. This often happens within a few hours, but nobody can name an exact time.

While you wait, do not worry and do not take hasty actions. The most common mistake in this situation is to send the payment again “just in case”. If the original transaction does confirm after all, you will end up with two charges. The address validity period for exchanges is described below, and typical problems with the amount can be read about in the article on underpayment and overpayment.

What RBF is and how it helps

RBF (Replace-By-Fee) is a mechanism of the Bitcoin network and some similar networks that allows you to replace an unconfirmed transaction with a new version that has a higher fee. The old version is cancelled, and the new one enters the queue with a better priority. The money stays with you until one of the versions is confirmed.

What is important to know:

• RBF is not available in all wallets. The wallet must support replacement, and the transaction must have been created with this option.
• Only an unconfirmed transaction can be replaced. Once it is included in a block, this is no longer possible.
• Use this feature following the instructions of your specific wallet. If you are not sure, it is better to wait or contact its support.
• If you paid for an order with a fixed amount, note that the network fee is paid on top of the order amount. Raising it should not reduce the amount that reaches the recipient.

What CPFP is and when it applies

CPFP (Child Pays For Parent) is a technique in which a new transaction spends an output of a not-yet-confirmed one and carries the increased fee. It is profitable for a miner to include both transactions in a block together, so the “parent” is confirmed along with the “child”.

This method can help if you have access to the unconfirmed output, for example in your own wallet where the change returned. If you sent funds to someone else’s address and no change came back to your wallet, you may not have this option. Sometimes the recipient can speed up the transaction too, if they have access to the output.

Both methods, RBF and CPFP, are technical in nature. Use them only if you understand what you are doing, and rely on the features of your wallet. A mistake can lead to extra fees.

How other networks behave

The techniques described above apply primarily to Bitcoin and similar networks. In other networks a stuck transaction looks different.

• Ethereum and compatible networks, including BNB Chain. Transactions go in order of their numbers (nonce). If one of them stays pending because of a low gas fee, the ones after it will wait too. Many wallets let you speed up or cancel such a transaction by sending it again with the same number and a higher fee.
• Tron. The fee on this network is tied to account resources. A transfer usually does not get stuck in the classic sense, but it may fail if resources are insufficient. In that case the explorer will show an error.
• Solana, Litecoin and other networks. Each has its own rules. Always check the status in the explorer of the relevant network.

Remember that USDT exists on several networks, and the speed and cost of the transfer depend on the network you choose. More on this in the article on choosing a USDT network.

What not to do

In a stressful situation it is easy to take actions that make things worse.

• Do not send the same payment again. While the first transaction may still confirm, sending again will result in two charges.
• Do not send funds to strangers “for speeding up”. Scammers in chats and comments often offer to “speed up” a transaction for a fee. Genuine paid acceleration from random people does not exist.
• Do not disclose your seed phrase or private keys. No genuine service or support specialist will ask for them. For wallet protection see the article on wallet security.
• Do not create a new order for the same amount until you have found out what happened to the first one. It makes it easier to get confused and harder to sort things out.

What to do during an exchange on BITWHITE

For an exchange on BITWHITE, a separate payment address is issued for each order, and it is valid for up to 2 hours. You need to send the exact amount and in the selected network. If your transaction is stuck and the address validity period is running out, the sequence of actions is as follows.

1. Find the txid of your transfer in your wallet or on the exchange.
2. Open the order page by its number or link: the order status and txid are shown there.
3. Check the txid in a blockchain explorer and make sure the recipient address matches the address from the order.
4. If the transfer is still in the queue, wait. Do not send the payment again.
5. If the address validity period has expired and the transfer is still waiting for confirmation, or was confirmed later, contact support.

A payment that arrives after the deadline, for a different amount or in a different network is processed manually by an operator through support. This does not mean the outcome is known in advance: the decision depends on the circumstances of the specific case.

What to tell support

The more complete the information, the faster the operator will sort it out. Official channels are listed on the “Contacts” page. Prepare:

• the order number in the format BW-…;
• the coin and the network you sent in;
• the exact amount sent;
• the transaction txid;
• the time of sending and, if you have it, a screenshot of the status from the explorer.

Provide only this data. The service never asks for a seed phrase or private keys and does not offer exchanges in private messages. If someone writes to you first and promises to “solve the issue”, that is a reason to be wary. The only official domain of the service is bitwhite.net. For signs of fakes, read the article on fake exchangers.

Common mistakes with a stuck transaction

• Sending a repeat payment before finding out the status of the first one.
• Panicking and closing the order, although the transaction is in the queue and will soon be confirmed.
• Network confusion: the transaction seems confirmed, but not in the network specified in the order. This is a different case, covered in the article on a network and address error.
• Ignoring the required number of confirmations: the transfer is in a block, but the payout has not arrived because there are not enough confirmations.
• Setting the minimum fee on a congested network to save money.
• Asking the first person you meet in chats for “help”.

Checklist: what to do if a transaction is stuck

1. Do not send the payment again.
2. Copy the txid.
3. Check it in the explorer of the relevant network.
4. Compare the address, amount and network.
5. Determine the status: in the queue, in a block or not found.
6. If it is in the queue, wait or use RBF or CPFP, if your wallet supports it.
7. If it is a transfer for an order, open it by number or link and compare the address validity period.
8. If necessary, write to support, giving the order number, coin, amount and txid.

The general procedure for an exchange is described in the step-by-step guide. If you are only planning an exchange, choose the network and fee in advance with a margin. You can start on the BITWHITE exchange page.

How this relates to exchanging on BITWHITE

On BITWHITE, the rate and the final amount you will receive are shown before the order is created, and the rate is fixed at the moment the order is created. A payment address is issued for each order and is valid for up to 2 hours. The payout arrives after the network collects the required number of confirmations. Their number depends on the network and is indicated in the order.

No registration is needed for an exchange, so you should save the order number (BW-…) and the order link: they let you see the status and txid. If a payment arrived after the deadline, for a different amount or in a different network, it is processed manually by an operator through support, and you do not need to pay again. It is not possible to promise a specific result in advance: everything depends on the circumstances of the order.