Level 2 · First stepsThe village#147

Stuck transactions and how to speed them up: only the person holding the key can push

A stuck Bitcoin payment is one whose fee is too low for the queue. The sender can replace it with a higher-paying version (replace-by-fee), or the receiver can spend the incoming coins with a high fee so miners take both (child pays for parent). If an exchange sent it, only the exchange can do either.

Grandma Rosa sent Anna a payment for the jam and left the smallest tip the scribe would accept. Three pages have been written since. Her note is still on the table, near the bottom of the pile.

She can't pull it back: every house has a copy of the note. But she can hand the scribe a new version of the same note, paying the same coins to Anna, with a bigger tip. Or Anna can pass on the coins she's waiting for with a big tip of her own, and the scribe, to collect it, has to write Rosa's note first.

That's how stuck payments get moving on Bitcoin. Nobody at a help desk can push them. Only someone holding a key can, by paying more.

What it is

A transaction is "stuck" when it waits in the mempool, the queue every node keeps, because its fee rate is below what miners are picking. "Why fees change every minute" explains why that line moves. There are two ways to raise your bid.

Replace-by-fee (RBF). The sender signs a new version of the payment that spends the same coins with a higher fee. Nodes swap the old one out. BIP 125, assigned its number in December 2015, set the original rules: the replacement must pay at least the original's total fee and pay for its own size on top (BIP 125).

Child pays for parent (CPFP). Someone who receives an output of the stuck payment spends it at once with a high fee. Optech describes it as spending "an output from a low-feerate unconfirmed transaction in a child transaction with a high feerate" (Bitcoin Optech). A miner can only collect the child's fee by including the parent too.

How it works: Rosa's 17 satoshis

The figures are real; Rosa's payment is an example.

  1. The payment. A simple payment with one input and two outputs takes 141 virtual bytes (mempool.space). Rosa offers 0.12 sat/vB: about 17 satoshis.
  2. Is it really stuck? On the evening of 18 November 2026, blocks 976,497 and 976,498 had a median fee rate of 0.12 sat/vB (mempool.space). Payments like Rosa's were confirming, just not in every block. Often "stuck" means "at the back of the queue".
  3. The target. On 19 November 2026, mempool.space suggested 2 sat/vB for the next block (mempool.space).
  4. Option one, RBF. Rosa signs a replacement at 2 sat/vB: 141 × 2 = 282 satoshis. That's more than 17 plus the charge for its own size, so nodes accept the swap. At €56,980.95 per bitcoin (CoinGecko, at 18 November 2026 prices), 282 satoshis is about 16 cents.
  5. Option two, CPFP. Anna spends the coins she's receiving in a child of the same size, 141 virtual bytes. For the pair to average 2 sat/vB, the two together must pay 282 × 2 = 564 satoshis. The parent pays 17, so the child pays 547: about 31 cents, at 3.9 sat/vB on its own.

RBF is cheaper because only one transaction takes up space. CPFP works when the sender can't or won't act.

Who can do what

The rules have changed under the hood. BIP 125 asked senders to flag a payment as replaceable with an input sequence number below a set line. The 18 November 2026 payment above carries 4294967293, below that line: flagged. Bitcoin Core 28.0, published on 2 October 2024, switched full replace-by-fee on by default (Bitcoin Core 28.0). Version 29.0, published on 14 April 2025, removed the option, "making full replace-by-fee the standard behavior" (Bitcoin Core 29.0). Nodes on that software accept a replacement whether or not the original was flagged (Bitcoin Optech).

What hasn't changed: you need the key. RBF needs the sender's key, CPFP the key to an output of the stuck payment. That's why, when an exchange sends your withdrawal, the exchange decides. Bitvavo, as one example, says on its deposits page that it can't speed up or slow down confirmations (Bitvavo).

And if nobody bumps it? A Bitcoin Core node on default settings keeps a waiting payment for 336 hours, two weeks, and uses at most 300 megabytes of memory for the queue (Bitcoin Core). Dropped isn't spent: the coins never left the sender's address.

Why it matters

  • You can fix a low fee yourself, if your wallet offers "bump fee" or "speed up". Check before you need it.
  • The receiver isn't powerless. If you're owed coins and the payment is stuck, CPFP is your lever.
  • Unconfirmed isn't paid. Ben's favourite trick: pay with a low fee, take the jam, then replace the payment with one back to himself. A seller who waits for the first confirmation never notices him. Good luck, Ben.

Where people get it wrong

  • "Send it again." A second payment spends different coins. If both confirm, you've paid twice.
  • "Support can push it through." No company controls the queue. Only a key holder can raise the bid.
  • "Cancel means the money comes back at once." A replacement that pays the coins back to yourself is the only real cancel, and it also has to confirm.
  • "It's been an hour, so it's lost." It's waiting. Look it up with its transaction ID, as "Transaction IDs: how to track a payment" shows.

Find the button before you need it

Open your wallet and look for "bump fee", "speed up" or "replace" next to a pending payment. If it's there, you can rescue your own low tip. If it isn't, set fees with care, because the queue is the only way out.

And if a stranger at the gate offers to "unstick" your payment for a fee and your seed phrase: the only thing that will speed up is your balance, on its way to him.

Frequently asked questions

Why is my Bitcoin transaction stuck?

Its fee rate is lower than what miners are picking from the queue. It stays in the mempool until the queue thins out, or until someone raises the bid with replace-by-fee or child pays for parent.

What is replace-by-fee (RBF)?

A way for the sender to replace an unconfirmed payment with a new version spending the same coins at a higher fee. Since Bitcoin Core 29.0, released on 14 April 2025, nodes running it accept such replacements by default, whether or not the original was flagged.

What is child pays for parent (CPFP)?

The receiver, or the sender with a change output, spends an output of the stuck payment in a new transaction with a high fee. Miners include both to collect the fee, so the pair's combined fee rate is what counts.

Can an exchange speed up my withdrawal?

Only the exchange can, because it holds the key that signed the payment. You can't bump it yourself. If you're the receiver and the coins land in your own wallet, you can use child pays for parent.

What happens if a transaction never confirms?

A Bitcoin Core node on default settings drops it after 336 hours, two weeks. The coins never left the sender's address, but anyone who kept a copy could broadcast it again, so the safe cancel is to spend the same coins in a new payment.

Sources

  1. David A. Harding and Peter Todd, BIP 125: Opt-in full replace-by-fee signaling
  2. Bitcoin Core 28.0 release notes (2 October 2024)
  3. Bitcoin Core 29.0 release notes (14 April 2025)
  4. Bitcoin Optech, Child pays for parent (CPFP)
  5. Bitcoin Optech, Replace-by-fee (RBF)
  6. Bitcoin Core source code, src/kernel/mempool_options.h (default mempool size and expiry)
  7. mempool.space API, transaction 19011ba7...4b9a (141 virtual bytes, input sequence number)
  8. mempool.space API, recommended fees (read on 19 November 2026)
  9. mempool.space API, blocks 976,493 to 976,507 (18 to 19 November 2026)
  10. Bitvavo, Confirmations when depositing crypto assets (example, read on 19 November 2026)
  11. CoinGecko, Bitcoin price in euros (house reference price for 18 November 2026)

Read next.