Why is my bitcoin transaction stuck with zero confirmations?

11 October 2026

Your Bitcoin transaction is stuck with zero confirmations because it has not yet been included in a block by miners. This usually happens because the fee you attached was too low relative to current network demand, or because the transaction is competing with many others for limited block space.

How bitcoin confirmations work

When you broadcast a transaction, it enters the mempool - a temporary holding area where unconfirmed transactions wait. Miners select transactions from the mempool, prioritizing those with higher fees per byte. Once a miner includes your transaction in a block, it receives its first confirmation. Each subsequent block built on top adds another confirmation.

A transaction with zero confirmations is valid but unprocessed. It has been seen by the network but not yet permanently recorded on the blockchain.

Common reasons a transaction gets stuck

Too low a fee

The most frequent cause. Every transaction competes for space in the next block. Miners naturally choose transactions offering the highest fee relative to their size in bytes. If your fee is below the market rate, miners will skip it in favor of better-paying alternatives.

Fee estimation depends on network congestion. During periods of high demand - such as during price volatility or major protocol events - the fee required for timely confirmation can increase sharply. A fee that would have worked an hour ago may now be too low.

The transaction is small or old-fashioned

Very small transactions (dust) or those using legacy (non-SegWit) addressing can be less attractive to miners. SegWit transactions are smaller for the same amount of data, meaning the same fee buys more "fee rate" (satoshis per byte). If your transaction uses a legacy address, it may need a higher absolute fee to compete.

Network Congestion

Bitcoin's block size is capped. When many users send transactions simultaneously, the mempool fills. Even transactions with reasonable fees may wait longer than usual simply because there are more transactions than blocks can accommodate in the short term.

Replace-by-Fee (RBF) not enabled

If your wallet does not support RBF, or you did not enable it when creating the transaction, you cannot easily increase the fee after broadcasting. This leaves you with fewer options to unstick it.

What you can do

1. check whether your transaction has RBF flagged

Look at your transaction in a block explorer (like mempool.space or blockchain.com). If it shows "RBF" or "opt-in RBF" enabled, you can replace it with a new transaction that pays a higher fee. This is called a fee bump.

• If RBF is enabled: Create a new transaction spending the same inputs but with a higher fee. Broadcast it. Miners will prefer the higher-fee version.
• If RBF is not enabled: You cannot replace it this way. Move to step 2.

2. Use Child-Pays-for-Parent (CPFP)

If you control the address that received the stuck transaction (the output), you can spend that unconfirmed output in a new transaction with a very high fee. Miners see that the new transaction requires the parent to be confirmed first, so they are incentivized to mine both.

• Send a new transaction from the receiving address back to yourself (or to another address you control) with a fee high enough to make the combined package attractive.
• Some wallets automate this process. If yours does not, you may need to use a tool or manually construct the transaction.

3. Wait

If the network is only temporarily congested, your transaction may eventually confirm as miners work through the backlog. Transactions with very low fees can sometimes wait hours or even days. In extreme cases, they may never confirm and will be dropped from the mempool after roughly two weeks (the default expiry period for most nodes).

If your transaction is dropped, the bitcoin returns to your wallet as if you never sent it. You can then try again with a higher fee.

4. Use a Third-Party Accelerator

Some mining pools offer transaction acceleration services, usually for a fee. These services manually include your transaction in a block they mine. Be cautious - some are legitimate, others are scams. Check reviews and only use well-known services.

How to Avoid Stuck Transactions in the Future

• Use a wallet that supports RBF and enable it by default. This gives you a fallback if fees spike.
• Check current fee estimates before sending. Sites like mempool.space show recommended fee rates for different confirmation times (e.g., next block, within an hour, within a day).
• For time-sensitive transactions, pay the "next block" fee rate, not the cheapest option.
• Use SegWit addresses (starting with bc1) to keep transaction size smaller, which reduces the fee needed for the same priority.

When to Worry

A transaction with zero confirmations is normal for minutes or even hours during busy periods. You only need to take action if:

• It has been several hours and the mempool backlog is not shrinking.
• The fee you paid is far below the current recommended rate.
• You need the transaction to confirm by a specific time (e.g., to meet a payment deadline).

Otherwise, patience often works. Bitcoin's network is designed to eventually include all valid transactions, even if slowly.

Back to bitcoin