Guide
Bitcoin Transaction Not Confirming? Causes and Fixes (RBF & CPFP)
The bottom line: unconfirmed usually means "the fee is too low + the mempool is congested" — and most of the time RBF or CPFP can get it moving
You sent bitcoin but it hasn't reached the recipient, and it just sits there "unconfirmed" (0 confirmations). In most cases, this simply means the fee rate you paid was low, so your transaction is stuck waiting its turn in a congested memory pool (mempool). First, take a breath and check the situation.
Key takeaways
- The main causes of an unconfirmed transaction are an insufficient fee and network congestion. Your balance hasn't disappeared
- Search for your transaction ID on a block explorer such as mempool.space to see its status
- The sender can use RBF (Replace-By-Fee) and the receiver can use CPFP (Child-Pays-For-Parent) to add fees and speed things up
- Avoid actions that could trigger a double-spend, such as re-sending the same funds to another address
Why it gets stuck
A bitcoin payment first enters the mempool (the waiting room for unconfirmed transactions) as an unconfirmed transaction. Miners prioritize transactions with a higher fee rate (sat/vB: satoshis per virtual byte), so transactions with a low rate get pushed back during busy periods. For more, see What is the mempool? and How Bitcoin transaction fees work.
First, check the status
- Copy the transaction ID (TXID) of your payment from your wallet
- Search for the TXID on mempool.space or a similar explorer
- "Unconfirmed" means it's still pending; if a block height is attached, it has been confirmed
By comparing the fee rate you paid with the level of fees currently being included in blocks, you can judge whether it's stuck because it's simply too cheap.
How to speed it up
| Method | Who uses it | How it works |
|---|---|---|
| RBF (Replace-By-Fee, BIP125) | Sender | Replaces the unconfirmed transaction with a version that pays a higher fee |
| CPFP (Child-Pays-For-Parent) | Receiver | Attaches a high fee to a "child" transaction that spends the received unconfirmed output, getting the parent pulled in along with it |
Recent versions of Bitcoin Core generally treat unconfirmed transactions as replaceable (full-RBF), but whether you can actually use RBF/CPFP depends on the wallet you're using. If your wallet has a "Raise fee," "Bump fee," or "Accelerate" button, you can use it.
What not to do
- Re-sending the same funds in a new transaction — even if the balance appears to show up twice, this causes a double-spend and only creates confusion
- Assuming you've "successfully cancelled" while it's still unconfirmed. A transaction with 0 confirmations can, in theory, still be reversed, so the receiving side should wait for confirmations
- Panicking and resending over and over
Also, if a low-fee unconfirmed transaction goes unincluded for a long time, it can naturally disappear (drop / expire) from nodes' mempools. In that case the funds simply remain at the sending address and aren't lost (if you've lost track of your funds, see also What happens if you lose your bitcoin?). For the basics of sending, see How to send bitcoin, and for how confirmations are counted, see What is a Bitcoin confirmation?.
Frequently asked questions
Does unconfirmed bitcoin disappear?
No, your balance does not disappear. A low-fee transaction lingers in the mempool, and if it isn't included for a long time it can be removed from nodes — but in that case the funds simply return to being available at the sending address.
What's the difference between RBF and CPFP?
RBF is a method where the sender replaces the unconfirmed transaction itself with a higher-fee version (BIP125). CPFP is a method where the receiver attaches a high fee to a child transaction that spends the received unconfirmed output, getting miners to include the parent transaction along with it.
If it isn't arriving, should I send to the same person again?
No. First check the status on a block explorer. Duplicate payments can lead to a double-spend or unexpected costs. Wait for confirmation, or consider speeding it up with RBF/CPFP.
Sources
- BIP125: Opt-in Full Replace-by-Fee Signaling — bitcoin/bips
- Replace-by-fee (RBF) — Bitcoin Optech
- Child pays for parent (CPFP) — Bitcoin Optech
- mempool.space FAQ
A note before you invest
This article is for informational purposes only and is not investment advice. Bitcoin carries risks including price volatility, hacking, and loss. Make investment decisions at your own responsibility and only with money you can afford to lose. Tax and regulatory rules can change, so always verify the latest information from official primary sources.
Sources
FAQ
- Does unconfirmed bitcoin disappear?
- No, your balance does not disappear. A low-fee transaction lingers in the mempool, and if it isn't included for a long time it can be removed from nodes — but in that case the funds simply return to being available at the sending address.
- What's the difference between RBF and CPFP?
- RBF is a method where the sender replaces the unconfirmed transaction itself with a higher-fee version (BIP125). CPFP is a method where the receiver attaches a high fee to a child transaction that spends the received unconfirmed output, getting miners to include the parent transaction along with it.
- If it isn't arriving, should I send to the same person again?
- No. First check the status on a block explorer. Duplicate payments can lead to a double-spend or unexpected costs. Wait for confirmation, or consider speeding it up with RBF/CPFP.
This article is informational only and is not financial, investment, or trading advice. Prices are reference snapshots and may be outdated. Always do your own research.
