If you sent or were sent Bitcoin and the funds have not appeared, the transaction is in one of three states: never broadcast, sitting unconfirmed in the mempool, or confirmed on-chain but not yet credited by your wallet or exchange. Your next step depends on which state applies. This guide walks through diagnosis, timing expectations, and the two safe acceleration methods available to senders and receivers.
Why hasn't my Bitcoin arrived, and how do I diagnose the problem?
Your Bitcoin has not arrived because the transaction either was never submitted to the network, is waiting in the mempool for miner inclusion, or has already been confirmed but your wallet or exchange has not yet updated your balance. Diagnosis starts with one question: do you have a txid, and what does a block explorer show?
The three-state diagnostic
Every pending Bitcoin receipt falls into one of these categories:
No txid available. The transaction was likely never broadcast. The sender's wallet may have failed to submit it, or a custodial exchange has not yet processed the withdrawal on-chain.
Txid exists, 0 confirmations on a block explorer. The transaction has been broadcast and sits in the mempool waiting for a miner to include it in a block.
Txid shows 1 or more confirmations. The transaction is settled on-chain. The issue is wallet sync delay, display lag, or your exchange's confirmation-count policy.
How to check
Ask the sender for the txid. Enter it into a block explorer such as mempool.space (source: Mempool.space) or blockstream.info (source: Blockstream). If the explorer returns nothing, the transaction does not exist on-chain. If it shows 0 confirmations, the transaction is in the mempool. If it shows 1+ confirmations, the Bitcoin network has settled the payment and the delay is on your receiving end.
"Pending" in wallet apps can mislead
Some wallets display "pending" before the broadcast actually completes. A wallet may show a local state that does not match the network. The sender's app crashing mid-broadcast, a failed validation check, or a custodial platform queuing withdrawals internally can all produce a "sent" label with no corresponding on-chain transaction. Without a txid that resolves on a block explorer, the transaction effectively does not exist on the Bitcoin network.
What are confirmations, and why do services require multiple?
A confirmation means your transaction has been included in a mined block on the blockchain. Each additional block mined on top increases the confirmation count by one. Confirmations measure depth in the chain, and depth determines how expensive it would be for an attacker to reverse the transaction.
Bitcoin targets one new block every 10 minutes on average. After one confirmation, your transaction is in the permanent ledger. After six confirmations (roughly one hour), reversing it would require controlling a majority of the network's hash power and outpacing the honest chain from six blocks behind (source: Bitcoin Wiki).
Why exchanges wait for more than one confirmation
Each additional block makes reversal exponentially harder. Exchanges set confirmation thresholds based on deposit size and their risk tolerance. Common policies:
Small deposits (under $1,000): 1-3 confirmations, typically 10-30 minutes.
Standard deposits ($1,000-$10,000): 3-6 confirmations, typically 30-60 minutes.
Large deposits (above $10,000): 6+ confirmations, sometimes up to 20 for very high values.
These thresholds are the exchange's risk policy, not a network limitation. Your funds are on-chain from the first confirmation; the exchange simply waits longer before crediting your account balance.
"Confirmed on-chain" vs "credited by exchange"
These are separate events. A transaction can show 4 confirmations on a block explorer while your exchange balance still reads zero because the platform requires 6. If the block explorer shows enough confirmations and your balance has not updated, check your exchange's stated deposit policy, then contact their support through the official website if the policy threshold has been met.
How does the mempool work, and why do transactions get stuck?
The mempool is a holding area where valid transactions wait before miners include them in a block. Every full node maintains its own copy. Miners select transactions from this pool based on fee rate, filling each block's limited space with the highest-paying transactions first.
Fee rate determines priority
Miners rank transactions by fee rate measured in satoshis per virtual byte (sat/vB), not by the total fee in dollars. A transaction paying 10,000 satoshis total might have a low fee rate if it is large (many inputs). A smaller transaction paying 3,000 satoshis might confirm faster because its sat/vB rate is higher. When checking whether your transaction's fee is competitive, compare its sat/vB against current mempool conditions on mempool.space, not the dollar amount shown in your wallet.
What causes a transaction to get stuck
Three scenarios account for nearly all stuck transactions:
The fee rate was set below current demand. During congestion spikes, transactions at 1-5 sat/vB can wait hours or days while 20+ sat/vB transactions confirm in the next block.
A sudden mempool spike occurred after the broadcast. A fee that was adequate an hour ago may now sit far below the median because trading volume surged.
The transaction depends on unconfirmed parent transactions. If your incoming payment spends an output that itself has not been confirmed, the entire chain waits together.
Can a transaction disappear from the mempool?
Yes. Most nodes purge transactions that remain unconfirmed for approximately 72 hours, though some extend this to 14 days (source: Tatum). Purging does not mean funds are lost. The sender's wallet still controls those coins and can rebroadcast or create a new transaction with a higher fee.
How can I speed up a stuck Bitcoin transaction?
Two protocol-level methods exist: Replace-by-Fee (RBF) for senders, and Child-Pays-for-Parent (CPFP) for receivers. Both are built into the Bitcoin protocol, supported by major wallets, and require no third-party service. Which one applies depends on whether you sent or are receiving the stuck payment. Our dedicated guide on RBF vs CPFP covers the full mechanics.
Replace-by-Fee (sender-side)
RBF lets the sender broadcast a replacement transaction that spends the same inputs but attaches a higher fee. The original transaction gets dropped from the mempool once the replacement propagates.
Requirements: the original transaction must have been sent with the RBF flag enabled (opt-in RBF), and the wallet must support fee bumping. Wallets that support RBF include Electrum, Bitcoin Core, and Sparrow.
Process: open the wallet's transaction history, find the pending transaction, select "bump fee" or "increase fee," set a new fee rate competitive with current mempool conditions, and broadcast the replacement.
Child-Pays-for-Parent (receiver-side)
CPFP lets the receiver create a new transaction that spends the unconfirmed incoming output with a high fee. Miners evaluate the combined fee rate of parent and child together and may include both in the same block.
Requirements: your wallet must support spending unconfirmed outputs, and you must be willing to pay a fee high enough to compensate for the parent's low rate across the combined transaction weight.
Process: create a new transaction from the unconfirmed output, set a fee rate significantly above the current median (enough that the averaged package rate is competitive), and broadcast.
When not to intervene
Do not attempt acceleration if the fee rate is already competitive and you have been waiting less than an hour. Do not rebroadcast raw transaction data you do not fully understand. Do not pay third-party "support agents" claiming they can release stuck funds. Do not share seed phrases or private keys under any circumstance.
In our experience verifying deposit flows across multiple platforms, most "stuck" transactions that already carry a competitive fee rate confirm within a few blocks once the next difficulty period smooths out congestion. Patience is often the correct fix when the sat/vB rate is reasonable. When we process BTC deposits at BloFin, the confirmation policy is published upfront so users know exactly how long to expect before funds are credited.
What should I do if my transaction is confirmed but funds still don't show?
If a block explorer shows your transaction with the required number of confirmations and your balance has not updated, the issue is on the receiving side, not the Bitcoin network. The most common causes are wallet sync delays, checking the wrong address, or an exchange policy requiring more confirmations than you expected. Each is fixable without any on-chain action.
Common causes
Wallet not synced. SPV wallets or light clients depend on a server to report the latest chain state. If the server is behind or your app has not refreshed, the balance display lags.
Wrong address checked. Verify the exact receiving address on the block explorer matches your wallet's deposit address character by character.
Exchange requires more confirmations than currently accumulated. Check the platform's deposit page for the stated threshold.
Funds sent to a different network or token format. BTC sent to a non-Bitcoin address or wrapped-BTC contract may be unrecoverable without platform cooperation.
Steps to resolve
Force a wallet refresh or full rescan from your wallet's settings. If using an exchange, check the deposit history page for any pending-credit indicator. If the confirmation count exceeds the stated policy and funds have not appeared after 24 hours, open a support ticket through the exchange's official website. Provide the txid and receiving address.
How do I avoid scams while troubleshooting a missing transaction?
People searching for help with pending Bitcoin are prime targets for impersonation scams. Scammers monitor forums and social media for users posting about stuck transactions and send unsolicited messages offering to "release" or "unlock" funds. No legitimate service operates this way, and any message requesting your seed phrase or private keys is fraudulent regardless of how official it appears.
Red flags
Anyone messaging you first about your transaction. Legitimate support does not initiate contact via DM.
Requests for your seed phrase or private keys. No legitimate service will ever ask for these.
"Support agents" requesting payment to "release" or "unlock" funds. This is always a scam.
Urgency framing ("your funds will be lost forever if you don't act now"). This is a manipulation tactic.
Websites that mimic block explorers but have slightly different URLs. Always type known URLs directly.
Safe practices
Use only the official support portal of your wallet provider or exchange (type the URL yourself, do not follow links from messages). Never share your seed phrase with anyone. Never pay upfront fees to strangers claiming they can accelerate your transaction. Our guide on common Bitcoin scams covers the full taxonomy of fraud patterns targeting new users.
Frequently asked questions
My transaction has 0 confirmations after 12 hours. Is my Bitcoin lost?
No. Zero confirmations means the transaction exists in the mempool but has not been included in a block. If the fee rate is far below current demand, it will wait until either congestion drops, the sender bumps the fee via RBF, the receiver uses CPFP, or nodes eventually purge it from the mempool after roughly 72 hours to 14 days. Purging returns control to the sender's wallet; the coins are never destroyed.
How do I know if my fee rate is competitive enough to confirm soon?
Check the transaction's sat/vB rate on a block explorer, then compare it against the current mempool fee distribution on mempool.space. If your rate falls within the range that recent blocks have been clearing, confirmation is likely within a few blocks. If it sits well below the lowest fee rate being mined, the transaction will wait until demand subsides or you accelerate it.
Can the receiver speed up someone else's transaction?
Yes, using CPFP (Child-Pays-for-Parent). If the receiver's wallet supports spending unconfirmed outputs, they can create a child transaction with a high enough fee to make the combined parent-child package attractive to miners. The receiver pays the acceleration cost out of the incoming funds, but gains faster access to the payment. Not all wallets expose this feature; Electrum and Bitcoin Core both support spending unconfirmed inputs.
What happens if a transaction is purged from the mempool?
The coins return to the sender's control as if the transaction never happened. The sender can then create a new transaction with a higher fee rate that matches current mempool demand. Nothing is lost and no action is needed from the receiver. The purge simply removes the unconfirmed transaction from nodes' memory pools, freeing the original inputs for reuse. Most wallets handle this automatically.
Does using a block explorer cost money or require an account?
No. Public block explorers like mempool.space, blockstream.info, and blockchain.com are entirely free to use and require no registration or account. You only need the txid (transaction ID) to look up any transaction's status, fee rate, and confirmation count. These tools read data directly from the Bitcoin blockchain and display it in a browser. They cannot modify, accelerate, or reverse any transaction.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Primary sources: Bitcoin Core mempool documentation, mempool.space fee data (April 2026), en.bitcoin.it confirmation mechanics. All facts independently verified.
Disclaimer: This content is for educational purposes only and does not constitute financial, investment, legal, or tax advice. Crypto assets are highly volatile and carry significant risk of loss. Always verify local regulations and consult a qualified professional before making financial decisions.