A Bitcoin orphan transaction is an unconfirmed payment that arrives in a node's mempool before its parent transaction does. The network can't validate it yet because it references an output that hasn't been confirmed, or even seen, on that particular node. The transaction sits in limbo until the parent appears or the node discards it.
Orphan transactions are different from plain stuck transactions. A stuck payment is one that has been received and validated but sits unconfirmed due to a low fee. An orphan is one that can't even be properly assessed yet because a piece of its spending history is missing. To understand why this matters, it helps to know a little about how Bitcoin tracks value.
Why Bitcoin transactions depend on their parents
Bitcoin doesn't work like a bank balance. Instead, every payment references specific unspent outputs (UTXOs) from previous transactions as its inputs. When you send Bitcoin, your wallet constructs a new transaction that says: "I'm spending output number 2 from transaction X, which sent 0.05 BTC to me three days ago." The network finds that prior transaction, checks the output, confirms you're authorised to spend it, and accepts the new payment.
If the network node you're connected to hasn't yet seen transaction X, it can't find that referenced output. Your new transaction becomes an orphan: technically valid, but unverifiable at that moment. The node stores it temporarily in a special pool and waits for the parent to arrive.
Common causes of orphan transactions
The most frequent cause is propagation delay. Bitcoin's peer-to-peer network has thousands of nodes spread around the world, and transactions don't reach all of them simultaneously. If two related transactions are broadcast in quick succession, the second one occasionally reaches a node before the first. That second transaction briefly becomes an orphan on that specific node until the first propagates through.
A second cause is chain of unconfirmed transactions. Some wallets and services chain multiple unconfirmed transactions together, where the output of one unconfirmed payment funds the next immediately. If any link in that chain is delayed or dropped, subsequent transactions become orphans. This is a known issue with certain fee-bumping approaches and with services that batch payments aggressively.
A third cause involves raw transaction construction errors. If someone manually crafts a transaction and references an output that doesn't exist or hasn't been broadcast yet, the result is an orphan that will never resolve on its own.
What happens to an orphan transaction?
Bitcoin nodes don't hold orphan transactions indefinitely. Most implementations keep a bounded orphan pool, typically around 100 transactions, and discard older ones as new orphans arrive. The Bitcoin Core client, which is the reference implementation maintained at bitcoin.org, uses this approach as a defence against memory-exhaustion attacks.
If the parent transaction arrives before the orphan is discarded, the node re-validates the orphan and moves it into the standard mempool. From there it competes with other transactions for inclusion in the next block. If the parent never arrives, the orphan is quietly dropped and the funds don't move at all. The sender's wallet should eventually show the payment as failed or unconfirmed, depending on the software.
Orphan transactions vs orphan blocks
The term "orphan" appears in two places in Bitcoin, and the meanings are distinct. An orphan transaction is an unconfirmed payment missing its parent output. An orphan block is a valid block that gets discarded because another block reached the network first and was built upon instead. The two share a name but describe separate network events. If you're researching the block-level version, the site has a dedicated explanation of what a Bitcoin orphan block is and why it happens.
Should beginners worry about orphan transactions?
For most everyday users, orphan transactions are invisible. Wallet software handles the sequencing automatically, and propagation delays on the modern Bitcoin network are short. You're unlikely to encounter one unless you're doing one of three things: chaining many unconfirmed transactions together, manually broadcasting raw transactions, or using very old or poorly built wallet software.
If you do see a payment stuck with no mempool activity and no record of it confirming, the practical steps are straightforward. Wait at least an hour for the parent transaction to propagate. Check a block explorer like mempool.space and search for the transaction ID. If the transaction doesn't appear at all, it was likely dropped as an orphan, and your wallet will eventually show the funds as unspent again. At that point you can resend with an appropriate fee rate.
Orphan transactions are a normal edge case in a decentralised network with no central coordinator. Understanding them won't change how most people use Bitcoin day to day, but it does give you a more accurate picture of what the network is actually doing when a payment behaves unexpectedly.