Encyclopedia How the network works · Entry 78
Why is my Bitcoin transaction still unconfirmed?
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Mempool | Different nodes need not have identical sets of pending transactions. | [1][4] |
| Timeout | A wallet’s display deadline is not a consensus cancellation. | [1][4] |
| Recovery | Fee replacement requires a transaction that meets the wallet and node conditions. | [2] |
Start with evidence, not a countdown
Check the transaction identifier, its inputs and the network on which it was sent. A payment still waiting for a wallet signature has a different problem from one accepted by a node but not yet mined. An explorer’s lack of a record does not prove that no other node has the transaction.
Look for an unconfirmed parent and for an alternative transaction spending the same input. The displayed fee rate is useful only when interpreted alongside transaction size and dependencies.
Understand the possible next steps
If the wallet supports a valid replacement, increasing the fee can create a more competitive conflicting transaction. If you control a suitable unconfirmed output, a child spend can change the economics of the dependent package. Neither method is guaranteed to be available.
Sending another unrelated payment can produce a second successful payment rather than repair the first. Before doing so, establish what the first transaction can still spend and whether a replacement or conflict already exists.
What ends the pending state
Inclusion gives the transaction a block location and one confirmation in that observed chain. Additional blocks increase depth; they do not turn a probabilistic settlement process into an absolute guarantee.
A node may also discard a pending transaction under its local policy. That deletion does not revoke a valid signature or prevent someone from broadcasting the same transaction again if its inputs remain spendable.
Direct answers
Questions people ask
Does waiting a fixed number of hours automatically return the coins?
No. Pending-transaction expiry is local node or wallet behavior. The relevant question is whether an accepted transaction has spent the inputs, not whether a timer has elapsed.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
An unconfirmed Bitcoin transaction has not yet been included in the chain being checked. It may be waiting because of its fee, a dependency, a conflict or incomplete propagation. First establish whether the transaction was broadcast and accepted; then use a supported replacement or dependent spend only if the wallet can construct one.
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.
Link to this claimMempool: Different nodes need not have identical sets of pending transactions.
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.
Link to this claimTimeout: A wallet’s display deadline is not a consensus cancellation.
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.
Link to this claimRecovery: Fee replacement requires a transaction that meets the wallet and node conditions.
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.
Link to this claimRevision history
- — Initial Bitcoin encyclopedia entry at this permanent URL.
- — Added reusable claims, explicit source locators, and matching Markdown and JSON. This publishing change does not itself establish factual verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Bitcoin Developer Guide: TransactionsBitcoin developer documentation contributors
UTXO inputs, transaction outputs, change and the difference paid as a fee.
Locator: P2PKH Script Validation; Transaction Fees And Change · Retrieved: 2026-10-02T17:03:41.190ZOpen source - bumpfee RPCBitcoin Core
Wallet-assisted replacement and the required fee and transaction conditions.
Locator: Arguments and result fields · Version / scope: Bitcoin Core 29.0.0 RPC · Retrieved: 2026-10-02T17:03:40.979ZOpen source - Bitcoin Core package policyBitcoin Core
Package fee accounting and policy for dependent transaction admission.
Locator: Package Mempool Acceptance Rules; Package Fees and Feerate · Version / scope: Bitcoin Core v29.0 · Retrieved: 2026-10-02T17:21:46.897ZOpen source - Bitcoin Core mempool maintenanceBitcoin Core
Node-local expiry and size-based eviction of unconfirmed transactions.
Locator: CTxMemPool::Expire; CTxMemPool::TrimToSize · Version / scope: Bitcoin Core v29.0 · Retrieved: 2026-10-02T17:55:16.998ZOpen source - walletcreatefundedpsbt RPCBitcoin Core
Input selection, fee units, change output, selected inputs and transaction funding.
Locator: Arguments and result fields · Version / scope: Bitcoin Core 29.0.0 RPC · Retrieved: 2026-10-02T17:03:40.827ZOpen source - Bitcoin Developer Guide: Block ChainBitcoin developer documentation contributors
Block headers, transaction Merkle trees and competing valid branches.
Locator: Proof Of Work; Block Height And Forking; Transaction Data · Retrieved: 2026-10-02T17:03:41.181ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “Why is my Bitcoin transaction still unconfirmed?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-stuck-transactions/