Why Is My Bitcoin Transaction Stuck?

A “stuck” Bitcoin transaction is almost always one thing: the fee was too low for the current network. Your coins aren't lost, and the transaction isn't broken — it's just sitting in line, waiting for a block that's willing to include a bid that small. Often the fix is simply patience. Sometimes you can nudge it along.

What “unconfirmed” actually means

When you send Bitcoin, your wallet broadcasts the transaction to the network, where it waits in the mempool — the shared pool of pending transactions. Miners build each block (~every 10 minutes) by selecting the highest fee-rate transactions first. If your sat/vByte rateis below what's currently winning, miners skip you in favor of higher bidders. You're not stuck — you're out-bid, and you stay in the pool until either the network quiets down enough that your rate wins, or the transaction expires. To see the queue you're standing in, learn to read the mempool.

Why it happens

• →Fees spiked after you sent. You picked a fine rate, then a surge of activity raised the going rate and left your bid behind — see why fees spike.
• →Your wallet underestimated. Some wallets default to a low fee, or use a stale estimate that doesn't reflect a sudden jump in demand.
• →You chose economy on a busy day. The lowest tier is great when the network is calm and slow when it's congested.
• →The transaction itself was heavy. Fees are charged per virtual byte, not per amount. A spend gathering many small inputs can be several times the size of a simple payment, so the same total fee buys a much lower rate — more in how transaction fees are calculated.

How long will it stay stuck?

There's no fixed deadline, but two clocks run in your favor. The first is demand: the queue drains in quiet hours, and a bid that looked hopeless in the afternoon often confirms overnight (see how long a transaction takes). The second is expiry: most nodes drop an unconfirmed transaction after roughly two weeks, at which point the coins are spendable from your wallet again. Some wallets tidy this up on their own; others make you hit “abandon transaction” first.

One wrinkle: an overloaded mempool evicts its lowest fee-rate transactions early — but an evicted transaction can be rebroadcast later by your wallet or anyone holding a copy. Treat expiry as a slow fallback, not a plan.

How to get unstuck

1. Just wait (usually the right call)

Network congestion is temporary. Demand falls overnight and on weekends, and when it does, the winning fee rate drops — often below your bid, at which point your transaction gets mined normally. For a non-urgent send, waiting a few hours (sometimes into the next weekend lull) is the simplest, zero-risk fix. Check the live mempool; if rates are falling toward your fee, you're close.

2. Replace-by-Fee (RBF) — bump the fee

If your wallet flagged the transaction as RBF-enabled when you sent it (many do by default), you can rebroadcast the sametransaction with a higher fee. It replaces the stuck one and jumps back up the line. Look for a “Bump fee,” “Increase fee,” or “Speed up” option in your wallet. This is the cleanest fix when it's available and the send is genuinely urgent.

3. Child-Pays-For-Parent (CPFP) — for incoming funds

Waiting on Bitcoin someone sent youthat's stuck? You can't edit their transaction, but if your wallet supports CPFP you can spend the unconfirmed incoming output in a new high-fee transaction. Miners must confirm the parent to collect the child's fee, so they pull both in together. It's more advanced and not in every wallet, but it's the standard tool when you can't use RBF. Torn between them? RBF vs. CPFP breaks down which to use.

What a bump actually costs: a worked example

Fees are priced per virtual byte, so the arithmetic is concrete. A typical single-input, two-output SegWit payment is around 140 vB. Every rate below is an invented example — always check the live rate before you act.

Suppose you sent that 140 vB transaction at 2 sat/vB — a 280-sat fee — and demand then surged so blocks are clearing at 20 sat/vB. You're out-bid ten to one. An RBF bump to 22 sat/vB re-prices the whole transaction: 140 × 22 = 3,080 sats. You don't pay both fees — the replaced transaction never confirms, so its 280 sats are never collected. Your total cost is the new fee alone.

A replacement must pay a higher total fee than the original, plus enough extra to cover relaying it again — about 1 sat/vB times its size — so a token nudge from 2 to 2.5 sat/vB usually gets rejected. Bump decisively: go straight to just above the next-block rate.

CPFP runs the same math less favorably. Rescue that 140 vB parent with a 110 vB child spend and miners judge the pair as a package: an effective 20 sat/vB across 250 vB takes 5,000 sats total. The parent brought 280, so the child must carry about 4,720 sats — roughly 43 sat/vB on its own. You're buying block space for two transactions, which is why RBF wins whenever both are available.

Mistakes that make it worse

• →Sending the payment again with different coins. The original doesn't vanish because you gave up on it. If both eventually confirm — and stuck transactions often do — you've paid twice. Replace or cancel the first before retrying.
• →Spending unconfirmed change. Every spend chained off a stuck transaction inherits its problem: nothing in the chain can confirm until the low-fee ancestor does, and nodes stop relaying chains past roughly 25 unconfirmed descendants.

How to avoid it next time

• →Check the live rate before sending. A 10-second glance at the current tiers prevents most stuck transactions — see what a good fee is right now.
• →Send during quiet windows when it's not urgent — fewer spikes mean fewer surprises. See the cheapest time to send.
• →Enable RBF in your wallet settings so you always have the option to bump.
• →Don't pick rock-bottom economy on a busy day unless you're genuinely fine waiting.

Quick answers

Can I cancel a stuck transaction?

If it's RBF-enabled, effectively yes: replace it with a higher-fee send back to your own address. Without RBF there's no reliable cancel — you wait for confirmation or expiry.

Do I lose the fee if it never confirms?

No. Fees are only collected by the miner who includes a transaction in a block. A dropped transaction costs nothing.

Can the recipient see it while it's stuck?

Yes — it's public in the mempool and their wallet will likely show it pending. But pending isn't settled: neither side should treat it as final. More on that in is it safe to send Bitcoin with a low fee.

Should this payment have been on Lightning?

For small or frequent payments, probably. Lightning settles in seconds for a tiny fraction of on-chain cost, and stuck transactions aren't a thing there. See Lightning vs. on-chain fees.

The bottom line

A stuck transaction is an underpaid fee, not a lost one. Wait it out when you can, bump it with RBF when you must, or use CPFP for incoming funds — and your coins are safe the whole time. Most of these never happen in the first place if you check the live network before you hit send.

Avoid the next one: the SatSaver fee tracker shows the current rate to use so your transaction lands the first time. Mempool data from mempool.space.