A laptop, transaction receipt and hourglass for investigating a delayed payment, editorial illustration
Foundations / GUIDE

A stuck transaction: wait, speed it up or cancel it

Work out where a payment is, why it is waiting, and how replace-by-fee, cancelling and child-pays-for-parent work, with the exact button in each wallet covered on this site.

Start reading
8 min readEnglish

Related walkthroughs

READING MODE

First, work out where the payment is

A payment that has not arrived can be in one of several places. It may never have been signed or broadcast. It may be waiting in the mempool, the queue of unconfirmed transactions that miners pick from. Or it may already be in a block. Each needs something different, so start with what your wallet reports.

  • No transaction ID. Nothing was broadcast. Check whether the transaction still needs signing, for example on a hardware wallet, or whether an exchange is still processing a withdrawal request.
  • A transaction ID with 0 confirmations. It is waiting in the mempool. The rest of this guide is about this case.
  • One or more confirmations. It is in a block and cannot be changed. If the recipient cannot see it, check that they gave you the right address and that their wallet has synced.

Use your wallet's own view first. Looking a transaction up on a public block explorer tells the site's operator you are interested in it. Your own node is better. Never paste your recovery words or extended public key into a website to investigate a payment.

Watch Navigating the mempool, explained in 2 minutes. Captions available.

Why a transaction gets stuck

Miners fill each block with the transactions that pay them most for the space, measured in satoshis per virtual byte (sat/vB). When more people are sending than a block can hold, low fee rates wait. A transaction sent at a quiet moment can be overtaken by a busy one an hour later.

A stuck transaction is not lost. It stays in the mempool until it confirms, is replaced, or is dropped. By default Bitcoin Core nodes drop a transaction after two weeks in the mempool, or sooner if their mempool fills up and it is among the lowest-paying. Since Bitcoin Core 29.1, released in September 2025, nodes by default relay transactions paying as little as 0.1 sat/vB, so very cheap transactions can wait a long time.

If there is no deadline, waiting is a reasonable choice. Ask the recipient whether they need it sooner before you pay more.

Bitcoin Core 29.1 release notes ↗

The three ways to speed it up

Replace-by-fee (RBF) sends a new version of your transaction that spends the same coins and pays a higher fee. Miners take the better-paying version and the original disappears. Only the sender can do this. The extra fee comes out of your change, or your wallet adds another coin.

Cancelling uses RBF too. The new version pays a higher fee and sends the money back to your own wallet. It is a race, as Liana and Envoy both warn in their apps. If the original reaches a block first, the payment goes through as normal.

Child-pays-for-parent (CPFP) spends a coin from the stuck transaction in a new transaction with a high fee. A miner who wants the new fee has to include the stuck one too, so the two confirm together. The recipient can do this with the coin they are receiving, and the sender can do it with their change.

Since Bitcoin Core 28.0, released in October 2024, nodes by default relay replacements whether or not the original transaction said it could be replaced, and 29.0 removed the option to turn that off. Most wallets still check for that signal, called opting in to RBF, before they offer to bump a transaction, and most switch it on by default. If your wallet has a setting for it, leave it on.

Bitcoin Core 29.0 release notes ↗ · Bitcoin Optech: replace-by-fee ↗ · Bitcoin Optech: CPFP ↗

Where to find it in your wallet

Every wallet names these buttons differently, and some leave tools out. Below is each wallet's own wording, checked against its source code on 17 November 2026. In every case, open the unconfirmed transaction from your history to find them.

  • Sparrow. Speed up with Increase Fee (RBF), cancel with Cancel Transaction (RBF), and use CPFP with Increase Effective Fee (CPFP). All three are on the Transactions tab, as a button on the unconfirmed transaction and in its right-click menu. RBF and cancel only work for transactions this wallet sent.
  • BlueWallet. Speed Up bumps a payment you sent, and on a payment you are receiving it uses CPFP. Cancel cancels. These tools only work in native SegWit single-key wallets, including ones linked to a hardware wallet, and not in vaults. Allow Fee Bump must have been on when you sent, and CPFP is not offered on watch-only wallets. When nothing else works, Speed Up links to the mempool.space accelerator.
  • Nunchuk. Replace-by-Fee and Cancel transaction are in the transaction's options menu. Cancel can send the money back to your wallet or to a different address. There is no CPFP button. Spend the unconfirmed coin with coin control and the fee screen shows the Effective package fee rate. Checked on the Android app.
  • Liana. Bump fee and Cancel transaction. There is no CPFP button, but when Liana spends your unconfirmed change it raises the fee to cover both and tells you so. A bump or cancel creates a new transaction that must be signed again.
  • Envoy. Boost and Cancel Transaction, then Proceed with Cancellation. No CPFP. With Passport Core or Passport Prime, your Passport signs the replacement before Envoy broadcasts it. Extra coins for a boost must be confirmed and unlocked, and you can boost the same transaction more than once.
  • Bitkey. Speed Up. No cancel and no CPFP. Every speed-up needs your Bitkey device, even for amounts under your limit for sending without it.
  • Bull Bitcoin. Accelerate. No cancel and no CPFP. It appears only for wallets that sign on the phone. The Replace-by-fee activated switch under advanced options is on by default. Leave it on.
  • Cake Wallet. Bump fee. No cancel and no CPFP. A transaction that spends unconfirmed coins does not opt in to RBF, so it cannot be bumped later.
  • Ashigaru. Boost transaction fee, then Increase tx fee. The same button uses RBF when it can and CPFP when it cannot. No cancel. RBF only works if Spend using RBF was on in settings before you sent.

Sparrow source ↗ · BlueWallet source ↗ · Liana source ↗ · Envoy source ↗

Hardware wallets and multisig

A replacement is a new transaction, so it needs new signatures. With a hardware wallet or signing device, you sign again the same way you signed the first time, by QR code, microSD card or cable. In a multisig, gather the same number of signatures as before. Check the amount, address and new fee on the device before you approve, as you would for any payment.

CPFP spends a coin you control, so it also needs your signature. A recipient using a hardware wallet can do it from Sparrow.

Lightning wallets

Lightning payments do not wait for blocks, so most of this guide does not apply to them. Some on-chain steps still can. Opening, resizing and closing channels are on-chain transactions.

  • Phoenix sends on-chain payments by resizing your channel. In the Android app, while one is unconfirmed it shows Tap to accelerate, which opens Accelerate my transactions (CPFP)..
  • ZEUS offers Speed up transaction only when it runs on LND, either embedded or on your own node. The LDK Node option, which ZEUS recommends for new wallets, has no speed-up.

After you have acted

A replacement has a new transaction ID. Save it next to the original, and give it to the recipient so you are both looking at the same payment. The original ID will never confirm.

Do not send a second, separate payment while the first is still pending. Both may confirm, and getting the extra back depends on the recipient. A transaction missing from one block explorer is not proof that it has been dropped everywhere.

Anyone who asks for your recovery words to speed up a transaction is trying to steal from you. No fee tool needs them.

Asking for help

A useful support request says which wallet you use, whether it has synced, whether the transaction has any confirmations and what you have already tried. Share the transaction ID only if you accept that it links you to the payment. Hide your balance and unrelated addresses in any screenshot.

When the problem is the network, not the fee

Some missing payments were never Bitcoin payments at all. Before withdrawing from a service, check that it sends bitcoin on the Bitcoin network, not a token on another blockchain, and that the address came from a Bitcoin wallet. Testnet and signet coins are for testing and have no value.

A Lightning invoice expires. If a payment fails, check whether it went through before you pay a fresh invoice. A Lightning address looks like an email address and only works with wallets that support it. If a service and your wallet disagree about the format, stop and ask for one your wallet supports. Coins sent to the wrong network can only be recovered, if at all, by the services involved.

Sources & further reading

Researched 17 November 2026. Software and services change: check the current documents before you act.

Managing your coins and fees → · Sparrow: build a wallet you can inspect → · BlueWallet: a clearer everyday wallet → · Liana: a wallet with a built-in recovery plan → · Phoenix →

Continue your path

One question leads to another.

01Bitcoin, without the vocabulary test02Managing your coins and fees0310 ways to lose your bitcoin

Find your next answer.

Search the complete field guide · Esc to close