Unconfirmed Bitcoin Transaction Checker

Is your bitcoin transaction stuck? Paste its transaction ID to see whether it's confirmed, how far back in the queue it is, and how to speed it up.

The checker needs JavaScript. The guide to unconfirmed transactions and fee bumping is below.

Why is my bitcoin transaction unconfirmed?

A transaction is unconfirmed until a miner puts it in a block. Until then it waits in the mempool, the queue of transactions every node keeps. A new block comes about every 10 minutes and has room for roughly 1 million virtual bytes (vB), so miners take the transactions that pay the most per vbyte first.

So the speed of a transaction depends on its fee rate, in satoshis per virtual byte (sat/vB), not on the amount sent or the total fee. If the mempool is busy and your wallet chose a low fee rate, newer transactions that pay more keep jumping ahead of yours. Right now wallets recommend about 1 sat/vB for a fast confirmation.

Your bitcoin isn't lost while it waits. The transaction either confirms, or, if it never does, nodes eventually drop it and the coins stay in the wallet that sent them.

How long does a bitcoin transaction take?

With a fee rate the next block accepts, the first confirmation takes about 10 minutes on average. Blocks are random, so sometimes it's 1 minute and sometimes 30 or more. Each later block adds one more confirmation.

  • 1 confirmation: enough for most small payments and many wallets.
  • 3 to 6 confirmations: what most exchanges wait for before crediting a deposit. 6 confirmations take about an hour.
  • Low fee rate: anything from an hour to several days, depending on how busy the mempool gets. The checker above shows how many blocks of better-paying transactions are ahead of yours.

How to speed up a stuck bitcoin transaction

  1. Replace-by-fee (RBF), if you sent it. Your wallet sends the same payment again with a higher fee, and the new version replaces the old one in the mempool. It gets a new transaction ID. The replacement must pay a higher fee rate and a higher total fee than the original. Wallets usually offer this only for transactions that signal RBF, although since Bitcoin Core 28 most nodes accept replacements of any unconfirmed transaction.
  2. Child pays for parent (CPFP), if one of its outputs is yours. The receiver, or the sender through their change output, spends the stuck coins in a new transaction with a high fee. Miners can only take the child together with its parent, so they look at the fee rate of both together. The child's fee has to cover the parent's shortfall too; the checker above works out about how much.
  3. Wait. When the mempool empties out, low-fee transactions confirm too. If it never confirms, most nodes drop it after 2 weeks, and the sender's wallet can spend the coins again.
  4. An accelerator. Some services, such as the mempool.space Accelerator, are paid to get mining pools to include a transaction. They're an option when you can't use RBF or CPFP, for example for a withdrawal from an exchange.

A withdrawal from an exchange or a custodial app is the exchange's transaction: you can't bump its fee yourself. Ask their support, or, if it's coming to your own wallet, use CPFP on the output you receive.

Fee bumping in popular wallets

How to speed up a stuck transaction in each wallet, and where it shows the transaction ID. The checker above works out the exact number to type for your transaction, in the unit your wallet asks for.

Trezor Suite

Transaction ID: On a computer, click the transaction to open "Details"; the ID is the "Tx ID" row (hover over it to copy it). In the mobile app, tap the transaction, open "Parameters" and tap "Transaction ID".

If you sent it

  1. Open your bitcoin account in Trezor Suite on your computer. The pending payment is in its list of transactions.
  2. Click "Speed up" on that payment.
  3. Click "New fee", then "Customize fee", and type the new fee rate in sat/vB.
  4. Click "Replace transaction", then check the fee increase on your Trezor and approve it.
  5. Back in Trezor Suite, click "Replace transaction" again to send it.

"Speed up" is in Trezor Suite for computers, not in the mobile app. If the account can't cover the higher fee, Trezor Suite takes it out of the amount sent, so the recipient gets a little less.

When it worked: The pending payment is replaced by the new one, with the higher fee and a new "Tx ID".

If you're receiving it

  1. In Trezor Suite on your computer, open the account that's receiving the payment, click "Send", then click "Coin control".
  2. Turn the switch on and tick only the coin from the stuck payment. It has a clock icon ("In pending transaction").
  3. In "Address", paste one of this account's own receive addresses (from "Receive"), and turn on "Send max".
  4. Open "Fee", click "Customize fee", and type the fee rate for the new transaction in sat/vB.
  5. Click "Review & send", confirm on your Trezor, then click "Send".

Trezor Suite only shows the new transaction's own fee rate, so use the number here; it already pays for the stuck payment too. This is in Trezor Suite for computers, not the mobile app.

When it worked: A second pending transaction, to yourself, appears. Both confirm together.

Ledger Wallet (formerly Ledger Live)

Transaction ID: Click the transaction to open "Operation details"; the ID is under "Transaction ID". On a phone, tap it to open "Transaction details".

If you sent it

  1. Click the pending payment to open "Operation details".
  2. Click "Speed up or Cancel".
  3. Choose "Speed Up" and click "Continue".
  4. Click "Advanced" and type the new fee rate under "Fees Amount" (in sat/vbyte), then click "Continue".
  5. Check the "Summary", click "Continue", and approve on your Ledger.

Ledger added this in March 2026, so if you don't see "Speed up or Cancel", update Ledger Wallet. With several pending payments, only the oldest can be sped up. The new fee has to be at least about 10% higher than the old one.

When it worked: Ledger Wallet says "Transaction sent", and the payment shows a new transaction ID.

If you're receiving it

Ledger Wallet can't speed up a payment you're receiving; it never spends coins that haven't confirmed. Connect your Ledger to Sparrow (free) and use child pays for parent there.

Sparrow

Transaction ID: On "Transactions", right-click the transaction's date and choose "Copy Transaction ID".

If you sent it

  1. Click "Transactions" on the left and find the payment marked "Unconfirmed".
  2. Right-click the word "Unconfirmed" in the "Date" column and choose "Increase Fee (RBF)". The "Send" tab opens with the new version filled in.
  3. Drag the "Range:" slider until "Rate:" shows the new fee rate. Or set the unit next to "Fee:" to "sats" and type the new total fee.
  4. Click "Create Transaction", then "Finalize Transaction for Signing".
  5. Click "Sign" (with a hardware wallet, click "Scan...", then "Sign" next to it, and approve on the device), then "Broadcast Transaction".

"Increase Fee (RBF)" only shows for a transaction that signals RBF (Sparrow's own payments do) and whose coins all came from this wallet.

When it worked: The new transaction shows on "Transactions" with "(Replaced By Fee)" added to its label.

If it doesn't signal RBF: child pays for parent through your change

  1. On "Transactions", right-click "Unconfirmed" in the "Date" column and choose "Increase Effective Fee (CPFP)". The "Send" tab opens with a payment back to your own wallet.
  2. Drag the "Range:" slider until the figure ending in "sats/vB (CPFP)", next to "Rate:", shows the rate for both together. Or set the unit next to "Fee:" to "sats" and type the fee for the new transaction.
  3. Click "Create Transaction", then "Finalize Transaction for Signing".
  4. Click "Sign" (with a hardware wallet, click "Scan...", then "Sign" next to it, and approve on the device), then "Broadcast Transaction".

When it worked: A second "Unconfirmed" transaction labelled "(CPFP)" appears on "Transactions". Both confirm together.

If you're receiving it

  1. On "Transactions", right-click "Unconfirmed" in the "Date" column of the incoming payment and choose "Increase Effective Fee (CPFP)". The "Send" tab opens with a payment back to your own wallet.
  2. Drag the "Range:" slider until the figure ending in "sats/vB (CPFP)", next to "Rate:", shows the rate for both together. Or set the unit next to "Fee:" to "sats" and type the fee for the new transaction.
  3. Click "Create Transaction", then "Finalize Transaction for Signing".
  4. Click "Sign" (with a hardware wallet, click "Scan...", then "Sign" next to it, and approve on the device), then "Broadcast Transaction".

When it worked: A second "Unconfirmed" transaction labelled "(CPFP)" appears on "Transactions". Both confirm together.

With a hardware wallet (Trezor, Ledger, Coldcard, BitBox, Jade…)

Connect it to Sparrow first. Sparrow only needs the device, never your recovery words.

  1. Close your hardware wallet's own app if it's open. Plug in your hardware wallet and unlock it.
  2. Download Sparrow from sparrowwallet.com and open it. Choose File > "New Wallet", type any name, and click "Create Wallet".
  3. Under "Script Type:", pick the one that matches your addresses ("Native Segwit (P2WPKH)" for bc1q…, "Taproot (P2TR)" for bc1p…, "Nested Segwit (P2SH-P2WPKH)" for 3…, "Legacy (P2PKH)" for 1…). Then click "Connected Hardware Wallet".
  4. Click "Scan...", approve on your hardware wallet if it asks, then click "Import Keystore".
  5. Click "Apply", then "No Password" (a Sparrow password only protects Sparrow's file). Wait until the payment shows as "Unconfirmed" on "Transactions".

Ledger: On the Ledger itself, open its Bitcoin app after you unlock it, and leave it open while you use Sparrow.

COLDCARD: If the COLDCARD refuses to sign because the fee is too big a share of the amount (by default it stops at 10%), you can raise its limit under Settings > "Max Network Fee".

Electrum

Transaction ID: In the "History" tab, right-click the transaction and choose "Copy" > "Transaction ID".

If you sent it

  1. Open the "History" tab and right-click the payment marked "Unconfirmed".
  2. Choose "Increase fee". In the "Bump Fee" window, leave "Method:" on "Preserve payment".
  3. To type the rate, click "Tools" and tick "Edit fees manually". Then type the new fee rate in the sat/vbyte box on the "New fee:" row.
  4. Click "OK", and enter your wallet password or confirm on your hardware wallet. Electrum signs and broadcasts it.

"Increase fee" only shows for a transaction that signals RBF (Electrum's own payments do). Otherwise the menu has "Child pays for parent" instead.

When it worked: Electrum says "Payment sent." and shows the new transaction ID.

If it doesn't signal RBF: child pays for parent through your change

  1. On "History", right-click the payment marked "Unconfirmed" and choose "Child pays for parent".
  2. In the "Child Pays for Parent" window, move the slider until "Total feerate:" shows at least the rate for both together. Or, with "Base unit:" set to "sat" (Tools > "Preferences" > "Units"), type the fee for the new transaction in "Fee for child:".
  3. Click "OK". In the window that opens, click "Sign", then "Broadcast".

When it worked: Electrum says "Payment sent." and a second unconfirmed transaction shows in "History".

If you're receiving it

  1. On "History", right-click the incoming payment marked "Unconfirmed" and choose "Child pays for parent".
  2. In the "Child Pays for Parent" window, move the slider until "Total feerate:" shows at least the rate for both together. Or, with "Base unit:" set to "sat" (Tools > "Preferences" > "Units"), type the fee for the new transaction in "Fee for child:".
  3. Click "OK". In the window that opens, click "Sign", then "Broadcast".

When it worked: Electrum says "Payment sent." and a second unconfirmed transaction shows in "History".

BlueWallet

Transaction ID: Tap the transaction. The "ID" row under "Details" shows it (tap to copy), or long-press it in the list and choose "Copy Transaction ID".

If you sent it

  1. Open the wallet and tap the pending payment.
  2. Tap "Speed Up".
  3. On "Speed Up (RBF)", tap "Custom" and type the new fee rate in sat/vByte.
  4. Tap "Create", then "Send now".

BlueWallet bumps fees itself only in its standard HD SegWit wallets (addresses starting bc1q). In other wallet types, "Speed Up" opens the paid mempool.space Accelerator instead.

When it worked: The payment is replaced by a new pending one with a new transaction ID.

If you're receiving it

  1. Tap the pending incoming payment.
  2. Tap "Speed Up".
  3. On "Bump Fee (CPFP)", tap "Custom" and type the rate for both transactions together, in sat/vByte.
  4. Tap "Create", then "Send now".

This works in BlueWallet's standard HD SegWit wallets (bc1q). If there's no "Speed Up" on your incoming payment, use the options below.

When it worked: A new payment to yourself appears, noted "Child pays for parent (CPFP)".

Blockstream app (formerly Blockstream Green)

Transaction ID: Open the "Transact" tab, tap the transaction, and copy it from the "Transaction ID" row.

If you sent it

  1. Open the "Transact" tab and tap the unconfirmed payment.
  2. Tap "Speed up Transaction".
  3. Choose "Custom" and type the new fee rate in sats/vB. On Android, tap "Network Fee" first. On iPhone, tap "Change speed" first, then "Save" and "Next".
  4. Slide "Slide to Send".

When it worked: The new version shows as pending in the transaction list.

If you're receiving it

The Blockstream app can't speed up a payment you're receiving.

Exodus

Transaction ID: On desktop, click the arrow beside the transaction to show its TXID. On mobile, tap the transaction; press and hold the TXID to copy it.

If you sent it

  1. Open your Bitcoin wallet in Exodus.
  2. Tap the stuck payment. On desktop, click the arrow beside it.
  3. Tap "Accelerate".
  4. Check the extra fee it shows, then confirm.

Exodus chooses the fee itself, and "Accelerate" only shows when the wallet has enough bitcoin left to pay it.

When it worked: The payment shows the higher fee and stays pending until a block takes it.

If you're receiving it

Exodus's help only describes "Accelerate" for payments you sent. If it shows on your incoming payment too, you can use it.

Trust Wallet

Transaction ID: Tap "History", tap the transaction, then "View on block explorer". The explorer page shows the transaction ID.

If you sent it

Trust Wallet can't speed up a bitcoin payment. Its "Speed Up" is only for Ethereum-style networks.

If you're receiving it

Trust Wallet can't speed up a bitcoin payment.

Coinbase Wallet

Transaction ID: Open the transaction from your activity. If it has a link to a block explorer, the transaction ID is the long code at the top of that page.

If you sent it

Coinbase Wallet's help only covers speeding up Ethereum-style (ERC-20) transactions, not bitcoin.

If you're receiving it

Coinbase Wallet's help only covers speeding up Ethereum-style (ERC-20) transactions, not bitcoin.

Atomic Wallet

Transaction ID: Open "History" and tap the transaction. Its details show the transaction hash, and "Tx hash" opens it on a block explorer.

If you sent it

Atomic Wallet can't speed up or cancel a transaction once it's sent; its help centre says so.

If you're receiving it

Atomic Wallet can't speed up a transaction.

Bitcoin.com Wallet

Transaction ID: Tap the transaction, then "View transaction on block explorer". The transaction ID is at the top of that page.

If you sent it

  1. Tap "Bitcoin" and choose the wallet with the pending payment.
  2. Tap the pending payment.
  3. Tap "Speed Up" in the yellow box.
  4. Check the extra fee it shows, then slide to confirm.

Bitcoin.com Wallet picks the new fee itself. If there's no "Speed Up" on the payment, it can't bump this one.

When it worked: The original payment is no longer pending, and the new version waits for a block instead.

If you're receiving it

Bitcoin.com Wallet can only speed up payments you sent.

Bitcoin Core

Transaction ID: On the "Transactions" tab, right-click the transaction and choose "Copy transaction ID".

If you sent it

  1. Open the "Transactions" tab and right-click the unconfirmed payment.
  2. Choose "Increase transaction fee". Bitcoin Core picks the new fee itself, and "Confirm fee bump" shows it as "New fee:".
  3. Click "Send", and enter your wallet password if it asks.
  4. To choose the rate yourself instead, open "Window" > "Console" and run: bumpfee TXID '{"fee_rate": FEE_RATE}'

If the wallet is encrypted, unlock it in the console first with walletpassphrase and your wallet password (never your recovery words).

When it worked: The new version shows as an unconfirmed transaction on "Transactions", with a higher "Transaction fee" in its details.

If you're receiving it

  1. On the "Receive" tab, click "Create new receiving address" and copy the address.
  2. Open "Window" > "Console".
  3. Run this, with your new address in place of NEW_ADDRESS: send '{"NEW_ADDRESS": AMOUNT}' null "unset" FEE_RATE '{"inputs":[{"txid":"TXID","vout":OUTPUT_INDEX}],"subtract_fee_from_outputs":[0]}'
  4. The console answers with "complete": true and the new transaction's "txid".

The Bitcoin Core window has no button for this, because it never offers unconfirmed incoming coins for spending, so it's done in the console. The rate is for both transactions together; Bitcoin Core works out the new transaction's fee from it.

When it worked: A second unconfirmed transaction appears on "Transactions".

Nunchuk

Transaction ID: Open the transaction, tap the more (⋯) icon at the top right, and choose "Copy transaction ID".

If you sent it

  1. Open the wallet and tap the payment showing "Pending confirmations".
  2. Tap the more (⋯) icon at the top right and choose "Replace-by-Fee".
  3. Under "New fee rate", type the new fee rate in sat/vB.
  4. Tap "Create transaction with new fee rate", then "Confirm and create transaction".
  5. Tap "Sign" and approve with your key or device, then tap "Broadcast transaction".

In a multisig wallet, every key that's needed has to sign the new version.

When it worked: The old transaction shows "Replaced", and the new one has a new transaction ID.

If you're receiving it

  1. Start a new payment from the wallet that's receiving, pick the coin marked "Unconfirmed" from the stuck payment, and send it to one of your own addresses.
  2. Tap "Customize transaction" and turn on "Manual fee rate".
  3. Type the fee rate for the new transaction in sat/vB. Nunchuk then shows the "Effective package fee rate" for both together.
  4. Create the transaction, tap "Sign", then tap "Broadcast transaction".

When it worked: A new pending payment to your own address appears. Both confirm together.

BitBoxApp

Transaction ID: Select the transaction to open "Transaction Details", then use the copy button beside "Transaction ID".

If you sent it

The BitBoxApp can't bump fees itself, but every payment it sends allows it; BitBox's own advice is to do it in Sparrow. Connect your BitBox02 to Sparrow (free) and bump it there.

If you're receiving it

The BitBoxApp won't spend coins from a payment that hasn't confirmed yet. Connect your BitBox02 to Sparrow (free) and use child pays for parent there.

Wasabi Wallet

Transaction ID: Right-click the transaction in the history and choose "Copy Transaction ID".

If you sent it

  1. Find the pending payment in the wallet's history.
  2. Click the rocket button on its row, or right-click it and choose "Speed Up Transaction".
  3. Check the cost under "Speeding up this transaction will cost you", then click "Confirm".
  4. Enter your Wasabi password if it asks.

Wasabi chooses the fee itself, and uses your change (child pays for parent) when it can't replace the payment. It can't do this for hardware-wallet or watch-only wallets.

When it worked: Wasabi says "Your transaction has been successfully accelerated."

If you're receiving it

  1. Find the pending incoming payment in the wallet's history.
  2. Click the rocket button on its row, or right-click it and choose "Speed Up Transaction".
  3. Check the cost under "Speeding up this transaction will cost you", then click "Confirm".
  4. Enter your Wasabi password if it asks.

Not for hardware-wallet or watch-only wallets.

When it worked: Wasabi says "Your transaction has been successfully accelerated."

Bitkey

Transaction ID: Tap the transaction under "Recent activity" (or "See All"), then tap the "Transaction ID" row to copy it.

If you sent it

  1. On the Home screen, tap the pending payment under "Recent activity".
  2. Tap "Speed Up".
  3. Check the "Speed up network fee" and the total, then tap the button at the bottom to send it.
  4. Hold your unlocked Bitkey to your phone to approve.

Bitkey picks the new fee itself, and always needs the Bitkey device for this.

When it worked: Bitkey says "Transfer sent", and the payment gets a new transaction ID.

If you're receiving it

Bitkey can't speed up a payment you're receiving.

Cake Wallet

Transaction ID: Open "History" and tap the transaction. Tap "Transaction ID" to copy it.

If you sent it

  1. In your Bitcoin wallet, open "History" and tap the pending payment.
  2. Tap "Bump fee".
  3. Under "Estimated new fee", choose "Custom" and set the new fee rate. Cake Wallet calls it sat/byte; it's the same number as sat/vB.
  4. Tap "Send", then swipe "Swipe to send".

If your change can't cover the higher fee, Cake Wallet may take it from the amount sent, and asks first. A payment that spent unconfirmed coins can't be bumped.

When it worked: Cake Wallet says "Transaction sent!".

If you're receiving it

Cake Wallet only bumps the fee of payments you sent.

Muun

Transaction ID: Tap the payment on the home screen. The details show "Transaction ID" (tap to copy).

If you sent it

Muun has no way to speed up a payment.

If you're receiving it

Muun has no way to speed up a payment.

COLDCARD

Transaction ID: COLDCARD has no list of transactions of its own. Use the wallet app you pair it with; in Sparrow, right-click the transaction and choose "Copy Transaction ID".

If you sent it

COLDCARD only signs; the fee is bumped in the wallet app you use with it. Connect your COLDCARD to Sparrow (free) and bump it there. If the COLDCARD refuses to sign because the fee is too big a share of the amount (by default it stops at 10%), you can raise its limit under Settings > "Max Network Fee".

If you're receiving it

COLDCARD only signs; this is done in the wallet app you use with it. Connect your COLDCARD to Sparrow (free) and use child pays for parent there.

Jade

Transaction ID: In the Blockstream app, tap the transaction; the ID is under "Transaction ID".

If you sent it

  1. In the Blockstream app, tap the unconfirmed payment.
  2. Tap "Speed up Transaction".
  3. On the "Increase fee" screen, tap "Network Fee", choose "Custom" and type the new fee rate.
  4. Check "Old fee" against "New fee", then tap "Sign Transaction".
  5. Approve it on your Jade.

When it worked: The new version shows as pending in the transaction list.

If you're receiving it

The Blockstream app can't speed up a payment you're receiving. Connect your Jade to Sparrow (free) and use child pays for parent there.

Electrum (Android)

Transaction ID: Tap the transaction. "Transaction ID" is under "Technical properties".

If you sent it

  1. Tap the unconfirmed payment, then tap "Bump fee...".
  2. In "Bump Fee", keep "Method" on "Preserve payment".
  3. Set the drop-down next to "New fee" to "Manual" and type the new fee rate in "Rate".
  4. Tap "Ok". The app signs and broadcasts it.

When it worked: The app says "Transaction was broadcast successfully".

If it doesn't signal RBF: child pays for parent through your change

  1. Tap the unconfirmed payment, then tap "Bump fee...". When the payment can't be replaced, this opens the child-pays-for-parent version.
  2. Move the slider until "Total fee rate" shows the rate for both together.
  3. Tap "Ok". The app signs and broadcasts it.

When it worked: The app says "Transaction was broadcast successfully".

If you're receiving it

  1. Tap the incoming unconfirmed payment, then tap "Bump fee...".
  2. Move the slider until "Total fee rate" shows the rate for both together.
  3. Tap "Ok". The app signs and broadcasts it.

When it worked: The app says "Transaction was broadcast successfully".

Robinhood Wallet

Transaction ID: Open the transaction in your history. If it has a link to a block explorer, the transaction ID is the long code at the top of that page.

If you sent it

Robinhood Wallet has no way to speed up a bitcoin payment.

If you're receiving it

Robinhood Wallet has no way to speed up a bitcoin payment.

Cash App

Transaction ID: Open the bitcoin withdrawal in your activity. Its receipt links to a block explorer, which shows the transaction ID.

Cash App sends its own withdrawals, so only Cash App can change the fee. Contact its support with the transaction ID. Cash App support.

Strike

Transaction ID: Open "Activity" and tap the withdrawal to see its receipt.

Strike sends its own withdrawals, so only Strike can change the fee. Contact its support with the transaction ID. Strike support.

River

Transaction ID: Open Activity (the clock icon on river.com, or the Activity icon in the app) and tap the send. It shows the transaction ID (TXID).

River sends its own withdrawals, so only River can change the fee. Standard and free withdrawals can take up to a day to be broadcast. Contact River's support with the transaction ID. River support.

Robinhood

Transaction ID: Robinhood gives a link to see the transfer on the blockchain. The explorer page shows the transaction ID.

Robinhood sends its own withdrawals, so only Robinhood can change the fee. Contact its support with the transaction ID. Robinhood support.

Coinbase

Transaction ID: Go to "Transactions", choose the transaction, then "View on block explorer". The explorer page shows the transaction ID.

Coinbase sends its own withdrawals, so only Coinbase can change the fee. Contact its support with the transaction ID. Coinbase support.

Binance

Transaction ID: On the website, open "Orders" > "Assets History" > "Withdraw". The "TxID" column shows it, 1 to 30 minutes after the withdrawal.

Binance sends its own withdrawals, so only Binance can change the fee. Contact its support with the transaction ID. Binance support.

Kraken

Transaction ID: In Kraken Pro, open "Portfolio" > "Spot" > "Funding transactions", click the withdrawal and copy the transaction ID from the pop-up.

Kraken sends its own withdrawals, so only Kraken can change the fee. Contact its support with the transaction ID. Kraken support.

Something else

Transaction ID: Open the transaction in your wallet and look for "Transaction ID", "TXID" or "Hash". If there's only a link to a block explorer, the ID is the long code at the top of that page.

If you sent it

  1. Open the pending payment in your wallet.
  2. Look for "Speed up", "Bump fee", "Increase fee" or "Accelerate".
  3. If it asks for a fee, enter the number below that matches what it asks for.
  4. Confirm and send it.

If there's no such option, your wallet can't bump the fee. See below.

If you're receiving it

  1. Open the incoming payment in your wallet.
  2. Look for "Speed up", "Bump fee", "Child pays for parent" or "CPFP".
  3. If it asks for a fee, enter the number below that matches what it asks for.
  4. Confirm and send it.

If there's no such option, your wallet can't do it. Ask the sender to speed it up, or see below.

If your wallet can't do it, pay to speed it up with the mempool.space Accelerator. Open your transaction on mempool.space and click "Accelerate". Mining pools then include it for a fee, which it shows before you pay; it has a sizeable service fee on top, so try everything else first. It works for any transaction, whoever sent it. Once you've paid, don't bump the fee yourself as well. Or wait: it confirms when fees drop, and if it never does, nodes drop it after about two weeks and the coins stay with the sender. Never type your recovery words (seed phrase) into a website or a wallet you don't know, to speed up a transaction or for anything else.

Menu names change between versions. If you can't find the option, look in the transaction's details screen.

Unconfirmed transactions: questions

Can I cancel an unconfirmed bitcoin transaction?
Only by replacing it before it confirms: a "cancel" in wallets such as BlueWallet or Sparrow is an RBF replacement that sends the coins back to your own wallet, with a higher fee. It works only if the replacement gets mined first. Once a transaction has one confirmation, it can't be cancelled.
Why does the transaction ID disappear after a fee bump?
RBF makes a new transaction with a new ID, and the old one is dropped. Look up the new ID in your wallet's transaction list. If you check the old ID here, it will say "not found".
What does "not found" mean?
Neither the blockchain nor the mempool has the transaction. It may have been replaced, dropped after waiting too long, never broadcast, or it may be a testnet transaction or a mistyped ID. If it was dropped or never broadcast, the coins are still in the sending wallet.
What is sat/vB?
Satoshis per virtual byte: the transaction's fee divided by its size. A typical payment (one input, two outputs, Native SegWit) is about 141 vB, so at 5 sat/vB it costs about 705 sats. Transactions with many inputs are bigger and cost more at the same fee rate.
How many confirmations do I need?
It's up to whoever receives the payment. Many wallets show a payment as settled after 1 confirmation; most exchanges credit deposits after 1 to 6. Each confirmation makes reversing the payment much harder.
Where does the data come from?
From public Bitcoin block explorers (Blockstream and mempool.space), fetched by our server, and the current fee rates from mempool.space. While a transaction is unconfirmed, the page checks it again each time a new block is found.