Orphan Transaction
Pronunciation: OR-fuhnd tran-ZAK-shun
Also known as: Orphaned Transaction
Definition
An orphan transaction is a transaction that a node cannot fully validate because a required parent transaction or referenced output is missing from its current view. The node may hold or reject it while waiting for the dependency. A transaction removed from the canonical chain by a reorganization is a different condition and should be tracked as reorg-removed rather than automatically labeled orphaned.
Overview
Meaning and scope
An orphan transaction is a transaction that a node cannot fully validate because a required parent transaction or referenced output is missing from its current view. The node may hold or reject it while waiting for the dependency. A transaction removed from the canonical chain by a reorganization is a different condition and should be tracked as reorg-removed rather than automatically labeled orphaned.
Mechanism and operation
This occurs most clearly in UTXO systems when a child arrives before the transaction that creates the output it spends. The node may keep the child in a temporary orphan pool, request the missing parent, or discard it according to local resource and policy limits. A dependency orphan can become valid once the missing parent arrives. Nodes may hold it briefly, request the parent, or discard it to limit memory and denial-of-service risk. A reorganization orphan has a different lifecycle: the transaction may return to the mempool, be included again in another block, conflict with a replacement transaction, or become invalid because one of its inputs was spent elsewhere.
Practical payment example
A transaction appears in a short-lived block branch that is later replaced. The merchant removes provisional credit and continues tracking the transaction if it returns to the mempool or another canonical block.
Operational checks
This differs from a Stale Transaction, which is usually old, expired, or no longer useful, and from an invalid transaction, which violates protocol rules. The orphaned status may be temporary and does not by itself prove fraud or failure. Software documentation should state whether the label concerns missing ancestry, removed block inclusion, or an application-level relationship.
Distinctions and limits
An orphan transaction is a transaction whose validation depends on a parent transaction or referenced output that the receiving node does not currently have.
Related reading
Related definitions: transaction, Stale Transaction.
Example
A transaction appears in a short-lived block branch that is later replaced. The merchant removes provisional credit and continues tracking the transaction if it returns to the mempool or another canonical block.
Comparison
An orphan transaction is a transaction whose validation depends on a parent transaction or referenced output that the receiving node does not currently have. Nodes may hold it briefly, request the parent, or discard it to limit memory and denial-of-service risk.
Key Takeaway
An orphan transaction is missing a required dependency; a transaction removed by a chain reorganization is a separate lifecycle condition.
Sources
- Bitcoin Developer Guide: Transactions — Bitcoin.org (2026-08-02)
- Bitcoin Developer Guide: P2P Network — Bitcoin.org (2026-08-02)
- Bitcoin Developer Guide: Block Chain — Bitcoin.org (2026-08-02)