Skip to content
Crypto Record

Crypto news across every chain

2026-11-21 08:37 UTCbc2fc3

Reasons a Bitcoin Transaction Stays Unconfirmed: Find the Fix

Reasons a Bitcoin transaction stays unconfirmed: a low fee rate, an unconfirmed parent, mempool eviction or relay policy can stall it. Diagnose the cause and choose a fix.

Crypto Record Editorial4 min read

Reasons a Bitcoin Transaction Stays Unconfirmed: Find the Fix

A Bitcoin transaction stays unconfirmed when miners have not selected it for a block or nodes are no longer relaying it; the cause is usually its fee rate, an unconfirmed parent, mempool eviction or relay policy. Miners generally prioritize transactions by fee rate per virtual byte (vB), so the next step is to find out whether the transaction is still in the mempool and what is holding it back.

Look up the transaction ID on mempool.space and compare its fee rate with the current fee estimates and projected blocks. Those estimates change as new transactions arrive and blocks are mined, so a rate that once looked competitive can fall behind. A transaction shown by your wallet but missing from mempool.space may have been evicted or never relayed; try rebroadcasting it, then check whether your wallet can safely create a replacement using the same inputs.

TeleSwap is a decentralized DeFi service for bridging and swapping Bitcoin and other assets across blockchains. Its teleswap app uses on-chain transaction verification and collateralized lockers. A TeleSwap deposit is not credited until the Bitcoin transaction confirms, so a stuck deposit is still waiting at this stage.

Fee rate below the current clearing level

A low fee rate can leave a transaction behind higher-paying entries in the mempool. The total fee matters, but miners compare the fee with transaction size: a larger transaction needs a larger total fee to offer the same rate. Check mempool.space’s live fee rates against your transaction’s rate; if the backlog is clearing above yours, the transaction may wait until demand falls or miners include lower-fee transactions.

If your wallet offers RBF, use it to send a replacement that spends the same inputs with a higher fee. BIP 125 describes opt-in replacement rules, while Bitcoin Core 28.0 made full RBF the default, allowing replacement without the original transaction signaling for it on nodes using that policy. Wallet and node support still matters. If you cannot replace the send, CPFP may help: spend an unconfirmed output you control, such as change, in a child transaction with a high enough fee to make miners consider the parent and child together.

Unconfirmed low-fee parent

A transaction can offer a competitive fee rate on its own and still stall because it spends an output from an unconfirmed parent. Miners need the parent confirmed before they can confirm the child, and the combined fee rate of both transactions may be unattractive. On mempool.space, inspect the transaction’s ancestors and their fee rates, not just the child’s.

If you control an output from the chain of unconfirmed transactions, CPFP can raise the combined fee rate. The child must pay enough to compensate for the package’s size and total fee shortfall. If the parent belongs to someone else or your wallet cannot build a child that spends it, ask the sender or service that created the parent to bump it.

Evicted on mempool expiry or a full mempool

A node can remove a transaction from its mempool when it expires or when space pressure forces it to drop lower-fee entries. Bitcoin Core’s default mempool expiry is 336 hours, or 14 days, though nodes can set a different period. Your wallet may keep showing the transaction in its history after nodes have dropped it.

If your wallet lists the transaction but mempool.space does not, first rebroadcast it and check whether it reappears. A rebroadcast works only if nodes still accept the transaction and its fee meets their current relay policy. If it stays absent, use your wallet’s replace or abandon-and-resend option to create a fresh transaction with an appropriate fee. Before resending, confirm the old transaction is no longer being relayed so you do not create conflicting payments.

Non-standard transaction not relayed

A transaction can fail to spread because it violates relay policy, even if it is not invalid under Bitcoin’s consensus rules. Nodes apply standardness rules to limit what they relay; a transaction using a non-standard form may be rejected before miners see it. A wallet may still display it as pending because it created or recorded the transaction locally.

Check the wallet’s broadcast error or node message, then inspect the transaction with a node or explorer. If the transaction is valid but non-standard, use wallet settings and transaction construction that produce a standard transaction, then broadcast the corrected transaction. Rebroadcasting the same transaction will not fix a policy rejection.