Bitcoin Transaction Stuck? What to Check Before You Act

A stuck Bitcoin transaction is usually a payment that has not yet entered a block, but an exchange withdrawal marked pending may not have been broadcast at all. Start with the transaction ID, confirmation status and who controls the sending wallet. Those three checks tell you whether to wait, ask the provider for help or investigate a supported fee-bumping option.

First, find out where the payment is waiting

Do not send the same payment again just because a status label looks worrying. Open the transaction details in the wallet or exchange that sent it. Look for a Bitcoin transaction ID, often called a TXID. An internal withdrawal reference is not necessarily a blockchain transaction ID.

Three different problems that can look like a stuck payment
What you see	What to check	Next step
Exchange says pending; no TXID	Whether the provider has broadcast the withdrawal	Contact the provider through its verified support channel
TXID found; zero confirmations	Fee rate, replacement status and wallet controls	Wait or review a supported fee bump
Confirmed on-chain; account not credited	Recipient address, required confirmations and deposit rules	Give the receiving provider the public TXID

A block explorer is a useful second view, not a reason to reveal your wallet backup. Paste only the public transaction ID. Our block-explorer guide explains the fields to read and the limits of what they prove.

Why a low fee can keep a transaction waiting

Miners have limited block space. The relevant comparison is generally the fee per unit of transaction size, displayed as satoshis per virtual byte, or sat/vB—not simply the dollar amount you paid. A larger transaction can pay more in total while offering a lower fee rate than a smaller one.

Check the current fee environment on our Bitcoin blockchain dashboard. Its estimate is context, not a reservation in the next block. Blocks arrive irregularly and competing demand changes. An estimate of ten minutes is not a deadline after which a payment has failed.

RBF: replace your outgoing transaction with a higher-fee version

Replace-by-fee, or RBF, lets the sender attempt a replacement that pays a higher fee. The sending wallet must support the operation, and the replacement must satisfy applicable network policies. Look for the wallet’s documented fee-bump or speed-up function rather than constructing an unrelated second payment.

Review the destination and replacement fee before signing. The transaction ID can change, so give the recipient the replacement ID if needed. A custodial exchange controls its own sending keys; having an account there does not let you personally replace its withdrawal transaction.

Trezor’s pending-transaction documentation explains its supported options. Our Trezor review and Electrum review provide product context, but the current wallet instructions take priority over a generic walkthrough.

CPFP: spend an output that depends on the waiting transaction

Child pays for parent, or CPFP, uses a new transaction spending an output from the unconfirmed transaction. A sufficiently attractive combined fee can encourage a miner to include both. The receiver may control the payment output; the sender may control a change output. Without an output you can spend, this option is not yours to initiate.

Here is a hypothetical package calculation. A parent is 200 vB and pays 400 sats. A child is 150 vB. At an assumed combined target of 10 sat/vB, the package needs 3,500 sats in total, so the child would need 3,100 sats. Its own fee rate would be about 20.7 sat/vB. This is arithmetic, not a live recommendation: wallet construction, other ancestors and policy limits can change the required fee.

The Bitcoin Optech CPFP reference describes the mechanism. Do not spend more in fees than the situation warrants just to remove an uncomfortable pending label.

When waiting is reasonable—and when to stop

If the destination is correct, the payment is not urgent and the wallet still tracks it, waiting may be reasonable. A transaction disappearing from one node’s mempool does not prove universal cancellation or a refund. Another node may still retain it, or it may be rebroadcast. Check the wallet’s current state before spending those inputs again.

If you see a wrong destination, an unfamiliar replacement or an unexpected request to sign, stop and investigate. Confirmation is not something customer support can reverse. Never provide a seed phrase, private key or remote access to someone offering to unlock a transaction.

Quick answers

Can the receiver increase the fee?

Sometimes, using CPFP when their wallet can spend the unconfirmed received output. The receiver cannot simply edit the sender’s signed transaction.

Will my bitcoin disappear if the fee is too low?

A low fee alone does not transfer coins to somebody else. It can leave a payment unconfirmed. Check the transaction and wallet state before taking further action.

Should I restore my wallet to fix a pending payment?

Restoring a wallet does not buy block space. Start with the public transaction status, not a recovery process.

Continue reading

Sources are linked alongside the relevant explanations. See our editorial standards and report a correction.