Guides

Bitcoin Transaction Stuck or Unconfirmed? (2026 Fix Guide)

Published April 18, 2026 Updated April 30, 2026 9 min read

Bitcoin transaction waiting in mempool concept with confused user editorial

A stuck, unconfirmed Bitcoin transaction is one of the most common and frustrating user experiences in crypto. You’ve sent Bitcoin, waited hours or even days, and nothing has happened. This guide explains why transactions get stuck, how to unstick them using RBF or CPFP, and how to prevent the problem in the future.

Why Bitcoin transactions get stuck

Unstick path: RBF when enabled, otherwise CPFP, or wait for lower fees — see wallet section below.

The fundamental cause: fee competition

Bitcoin has limited block space (~1-2 MB per block, every ~10 minutes). More transactions are created than can fit in each block. Miners choose which to include, typically selecting the highest-fee-per-byte transactions first.

If your transaction’s fee is below the current threshold, it sits in the mempool (memory pool of unconfirmed transactions) waiting. If fees drop and yours becomes competitive, it confirms. If fees stay high for extended periods, your transaction just waits.

Typical scenarios causing stuck transactions:

Sending during high-traffic periods:

Bull markets, NFT mints, ordinal inscriptions increase demand
Fees can spike from $1 to $100+ during peak demand
Transactions sent at normal-period fees get stuck when demand spikes

Wallet using outdated fee estimates:

Wallets estimate fees based on recent mempool data
Rapid fee changes can outpace wallet estimates
Especially problematic during market volatility

Manual fee specification too low:

User selects a low fee to save money
Fee is below the current threshold
Transaction sits unconfirmed

Long transactions:

Transactions with many inputs are larger (more bytes)
Need higher absolute fees to match per-byte rates
Can become competitive lower than expected

Dust-limit issues:

Very small outputs (below ~546 satoshis) can cause rejection
Different from stuck — transaction may never propagate

How to tell if your transaction is stuck

Check the transaction on a block explorer:

mempool.space (best for fee visibility)
blockstream.info
blockchain.com

Key information:

Fee rate (sat/vB): Your transaction’s fee per virtual byte
Position in mempool: Where your tx sits relative to current block inclusion
Mempool depth: How many transactions are competing
Estimated confirmation time: Based on current conditions

Signs it’s stuck:

Not confirmed after 1+ hour during normal conditions
Not confirmed after 3-4 hours during peak conditions
Fee rate is significantly below current block minimum
Mempool position is very far back

Signs it’s just slow:

Fee rate is near the threshold
Other similar-fee transactions are confirming
Short-term fee spike that’s expected to resolve

Solution 1: Replace-By-Fee (RBF)

RBF is the cleanest solution for stuck transactions when available.

Requirements for RBF

Transaction must be sent with RBF enabled:

BIP-125 opt-in feature
Most modern wallets enable by default (Sparrow, Electrum, Ledger Live, etc.)
Some older wallets don’t support it
Transaction’s nSequence field must indicate RBF

You must be the sender: Only the sender can replace a transaction. Recipients use CPFP instead.

The original transaction must still be unconfirmed: Once confirmed, no replacement is possible.

How to execute RBF

In wallet software with built-in RBF:

Open wallet (Sparrow, Electrum, most modern wallets)
Find the stuck transaction in your history
Select “Bump fee” or “Increase fee” option
Set new higher fee rate
Confirm new transaction
Wallet broadcasts the replacement

What happens:

New transaction has same inputs but higher fee
Miners prefer the higher-fee version
Original transaction drops out of mempools
Recipient sees the new transaction (usually same amount)

Typical RBF fee increase:

Original fee was too low
Check current mempool fees
Set new fee ~20-50% above current block-inclusion threshold
Ensure new fee exceeds original fee

RBF limitations

Some services don’t accept RBF:

Some exchanges ignore transactions marked as RBF
Specifically, they wait for confirmation to credit
RBF doesn’t break this — it just extends the wait

Cost: You pay the new fee (not the original + new). But the total is more than you initially budgeted.

Privacy implication: RBF creates on-chain evidence of fee bumping. Minor privacy concern but exists.

Solution 2: Child-Pays-For-Parent (CPFP)

CPFP is the solution when you’re the recipient or when RBF isn’t available.

How CPFP works

Basic principle:

Your stuck incoming transaction has unconfirmed outputs
You create a new transaction spending those unconfirmed outputs
Your new transaction’s fee rate is set high enough to make the combined (parent + child) average fee attractive to miners
Miners can only include the child if they include the parent — so they include both

Example:

Incoming stuck transaction: 100 KB, fee 1,000 sat (10 sat/vB, too low)
Create child transaction: 10 KB, fee 10,000 sat (1,000 sat/vB, high)
Combined: 110 KB, fee 11,000 sat, ~100 sat/vB average
100 sat/vB makes parent attractive → both confirm

When to use CPFP

You’re the recipient of a stuck transaction: The most common use case. Sender’s transaction is stuck, you need it confirmed.

You’re the sender but wallet doesn’t support RBF: Can create CPFP by creating a new transaction from the change output.

Multiple stuck transactions from same source: One CPFP on the most recent can unstick a chain.

How to execute CPFP

Prerequisites:

Wallet that supports spending unconfirmed outputs
Sparrow, Electrum, Bitcoin Core, and others support this
Some wallets (certain mobile wallets) don’t allow it

Process:

See the stuck incoming transaction in your wallet
Create a new send transaction
Wallet should allow using the unconfirmed output as input
Set a very high fee for the new transaction
Send it (usually back to yourself, to a different address)
Both transactions should confirm together

Calculating the right fee:

Check current fee rates (mempool.space gives good data)
Child fee rate × (parent size + child size) should equal what you want the combined fee to be
Err high — better to overpay slightly than stay stuck

CPFP limitations

You pay an additional transaction fee:

Both the original fee and the new child fee
Not just the difference
Can be expensive during high-fee periods

Some wallets don’t handle it well:

Can appear confusing in transaction history
Some wallets may balk at spending unconfirmed outputs

Requires technical capability:

Less intuitive than RBF
More opportunities for user error

Solution 3: Wait for fees to drop

Sometimes the best action is no action.

When waiting makes sense:

Fee spike is temporary (nights, weekends, post-hype periods)
Transaction fee is close to current threshold (small drop will include it)
No urgency on confirmation timing

Fee cycles:

Weekdays often busier than weekends
US/European business hours busier than Asian overnight hours
Post-bull-market dumps reduce congestion
NFT mint and ordinal cycles create temporary spikes

Tracking via mempool.space:

See current mempool size
See fee distribution
Project future inclusion timing
Monitor your specific transaction

Risk of waiting:

Transaction could drop from mempool after ~2 weeks
Opportunity cost of tied-up funds
Anxiety of waiting

Solution 4: Let it drop

If none of the above work and you can afford to wait, let the transaction drop out of mempools:

How this works:

Bitcoin Core nodes discard transactions after ~2 weeks
Once sufficient nodes discard, your transaction effectively no longer exists
Your original Bitcoin (the inputs) becomes spendable again
You can send again with higher fees

Downsides:

Long wait (2+ weeks)
Some nodes may still hold the transaction
If dropped unevenly, could cause issues

When this is appropriate:

Very low-value transaction where RBF/CPFP costs don’t make sense
You have no urgency
Fees are currently high but expected to drop before the 2-week window

Preventing stuck transactions

Use current fee estimates

Dynamic fee estimation: Most modern wallets check current network conditions. Ensure yours is doing this:

Fees should update based on real-time mempool data
Estimates should reflect current demand
Options like “economic”, “normal”, “priority” typically correspond to different confirmation time goals

Fee estimation services:

mempool.space provides recommended fees
bitcoinfees.info (historical)
Built into most wallet software

When to bump fee:

Fee spike in progress
Tight timing requirement
Unfamiliar with wallet’s default behavior

Enable RBF on all transactions

Set as default:

Ensures you can always bump fees if needed
No downside for most use cases
Recipients generally aware that RBF transactions can be replaced

Check wallet settings:

Sparrow: RBF on by default
Electrum: Toggle available
Ledger Live: RBF generally enabled
BlueWallet: Settings option

Avoid sending during peak congestion

When to expect high fees:

Major NFT mints
Ordinal rush periods
Bitcoin ETF approvals or major regulatory news
Bull market fomo peaks

When fees are typically low:

Weekend evenings
Asian overnight hours (from Western perspective)
Post-bearish news periods
Mid-week daytime (not ideal but better than late evening)

Use Lightning for small transactions

Lightning Network:

Off-chain payment layer
Sub-cent fees
Instant confirmation
Good for small payments, bad for large transfers

When Lightning beats on-chain:

Transfers under $100
Need for immediate confirmation
Recurring or streaming payments

Batch transactions

For senders making multiple transactions:

Combine multiple outputs into one transaction
Single fee instead of multiple fees
Exchanges, services, and power users benefit most
Requires wallet support for batching

For individual users:

Less common, but possible with some wallets
Save fees on multiple outgoing transactions

Specific wallet guidance

Sparrow Wallet

RBF support: Yes, by default. Fee bump: Right-click unconfirmed transaction → “Increase fee (RBF)” CPFP support: Yes, allows spending unconfirmed outputs.

Electrum

RBF support: Yes, can be toggled per transaction. Fee bump: Right-click transaction → “Child pays for parent” or “Increase fee” Advanced options: Full control over transaction parameters.

Ledger Live

RBF support: Yes, in most transactions. Fee bump: Limited native support; may need Sparrow or Electrum with Ledger hardware. For Bitcoin specifically: Consider using Sparrow/Electrum with Ledger for full control.

Trezor Suite

RBF support: Yes. Fee bump: Available in transaction details. Works well for most use cases.

Coinbase Wallet (mobile)

RBF support: Limited in mobile app. Fee bump: May need to use alternative wallet software. Consideration: If using Coinbase Wallet, have a backup plan for stuck transactions.

Exchange wallets

Coinbase (centralized): Exchange handles fees internally; stuck transactions rare for exchange-initiated sends.

Binance: Similar to Coinbase.

For exchange withdrawals: If exchange transaction is stuck, contact exchange support. They typically handle fee bumping on your behalf.

A stuck Bitcoin transaction is frustrating but almost always resolvable. RBF is the cleanest solution when available (requires sender action). CPFP works when you’re the recipient or when RBF isn’t available. Waiting works if you have no urgency. And letting transactions drop back to your wallet works for very low-value situations. The real win is prevention: use current fee estimates, enable RBF, avoid sending during peak congestion, and consider Lightning for small payments where appropriate.

This article is for informational purposes only and is not financial advice. Bitcoin transaction operations carry risks including potential fee overpayment. Cryptocurrency investments carry substantial risk, including total loss.

Frequently asked questions

Why is my Bitcoin transaction unconfirmed for hours?

Your Bitcoin transaction is unconfirmed because the fee you paid is too low for current network demand. Miners prioritize transactions with higher fees, so if your fee is below the current threshold, your transaction sits in the mempool (unconfirmed transaction pool) waiting for either higher fees to drop or a quieter period when miners include lower-fee transactions. Common causes: sending during high-traffic periods, using wallet default fees during congestion, or wallet miscalculating needed fee.

What is RBF (Replace-By-Fee)?

RBF is a feature that lets you replace an unconfirmed Bitcoin transaction with a new version paying a higher fee. The original transaction must have been sent with RBF enabled (most modern wallets do this by default). You create a new transaction with the same inputs but higher fee; miners prefer the higher-fee version, and the original transaction drops out of mempools. RBF is the cleanest solution for stuck transactions if available.

What is CPFP (Child-Pays-For-Parent)?

CPFP is a technique where you (the recipient) spend the unconfirmed incoming transaction’s output by creating a new ‘child’ transaction with a high enough fee to cover both transactions. Miners must include the parent to mine the child, so the combined fee rate makes the parent attractive. CPFP works when RBF isn’t available — especially useful when you’re receiving Bitcoin and the sender can’t or won’t do RBF.

Can an unconfirmed Bitcoin transaction disappear?

Yes. Unconfirmed transactions can drop out of mempools if nodes decide to discard them (typically after a few weeks of non-confirmation) or if a conflicting transaction gets mined instead. If your transaction drops completely, your original Bitcoin returns to your wallet and becomes spendable again. This isn’t a loss — but it can be confusing if you don’t know what happened. Track your transaction via mempool.space or similar to see its status.

How long can Bitcoin transactions stay unconfirmed?

Most mempools will hold unconfirmed transactions for 2-4 weeks before discarding them (this is a node policy, not a protocol rule). During that window, transactions can confirm whenever fees drop enough. After discard, the transaction effectively never happened — the Bitcoin returns to the sender’s wallet. However, ‘stuck for weeks’ is usually a sign to take action rather than wait: use RBF or CPFP to accelerate, or let it drop and retry with higher fees.