Definition
Orphan Block is a valid block that was solved by a miner but never became part of the chain the rest of the network agreed to extend, so its block reward is forfeited. It happens when two miners find a block at nearly the same block height and the network ultimately keeps only one of them.
Also known as: stale block, detached block, or (more loosely) a reorg casualty. In everyday mining conversation “orphan” and “stale block” are often used interchangeably, though purists draw a fine distinction between the two.
How an orphan block happens
Bitcoin only ever rewards one block per height. When two miners broadcast competing solutions at roughly the same moment, the network temporarily holds two candidate tips. Nodes follow the longest chain rule (more precisely, the chain with the most accumulated proof of work), so the next block to arrive effectively casts the deciding vote. The losing branch is abandoned, and the block that did real work but lost the race becomes an orphan.
The usual culprit is propagation delay: it takes a finite amount of time for a freshly found block to ripple across the global peer-to-peer network. While that block is still in flight, another miner who has not yet heard about it can solve the same height. The bigger the network and the slower the link, the wider this window. The transactions inside an orphaned block are not lost — they simply return to the mempool and get mined into a later block — but the block reward for the orphaned solution evaporates.
Orphan vs. stale: a precise distinction
Strictly speaking, a true orphan in Bitcoin Core terminology was a block whose parent the node had not yet seen — an old concept from early clients. In modern usage, the block that loses a same-height race and gets dropped is more accurately a stale block, the result of a one-block reorg. Either way, the practical outcome for the miner is identical: the work was valid, the network rejected it, and there is no block subsidy or transaction fees to collect. This is why coinbase rewards cannot be spent until the block reaches a safe number of confirmations — pools typically wait 120 blocks of maturity before treating a reward as real, precisely because a young block could still be orphaned.
Why a home ASIC miner should care
For day-to-day mining the orphan rate on Bitcoin is very low — a fraction of a percent of blocks — so it rarely dents the economics of running an ASIC in a pool. But the concept is not academic if you run a Bitaxe or any rig in solo mining mode. When you solo-mine, you are betting on landing the entire reward yourself; if your block is the one orphaned, all-or-nothing becomes nothing. Choosing a node and pool endpoint with low latency, and keeping your own Bitcoin node well-connected, shrinks the propagation window that produces orphans in the first place.
Pool payout logic bakes this risk in directly. Under PPLNS accounting, orphaned blocks are simply not paid out — the pool only distributes rewards for blocks that survive to maturity. This also clears up a common confusion at the hardware level: the “stale shares” your miner reports in its dashboard are a related but separate idea. A stale share is work submitted against an old job after a new block already arrived (network latency can cause your locally accepted shares to be rejected by the pool). An orphan block, by contrast, is a full block that was valid network-wide yet still lost the chain race. Understanding both helps you read your dashboard honestly rather than blaming your firmware for losses that are really a function of network timing.
If you want to experience this race first-hand, our Bitaxe hub walks through low-power solo setups, and the gear in our miner catalogue covers everything from a single lottery node to a full home mining stack. Every layer you self-host — your own node, your own pool — is one more layer decentralized, and one more way to keep your blocks from being orphaned.
Related terms: Stale Block, Longest Chain Rule, Propagation Delay, Confirmations, Solo Mining, Block Reward
In Simple Terms
A valid block rejected by the network because a competing block at the same height was accepted first.
Orphan Block is a valid block that was solved by a miner but never became part of the chain the rest of the network agreed to extend, so its block reward is forfeited. It happens when two miners find a block at nearly the same block height and the network ultimately keeps only one of them.
Also known as: stale block, detached block, or (more loosely) a reorg casualty. In everyday mining conversation "orphan" and "stale block" are often used interchangeably, though purists draw a fine distinction between the two.
How an orphan block happens
Bitcoin only ever rewards one block per height. When two miners broadcast competing solutions at roughly the same moment, the network temporarily holds two candidate tips. Nodes follow the longest chain rule (more precisely, the chain with the most accumulated proof of work), so the next block to arrive effectively casts the deciding vote. The losing branch is abandoned, and the block that did real work but lost the race becomes an orphan.
The usual culprit is propagation delay: it takes a finite amount of time for a freshly found block to ripple across the global peer-to-peer network. While that block is still in flight, another miner who has not yet heard about it can solve the same height. The bigger the network and the slower the link, the wider this window. The transactions inside an orphaned block are not lost — they simply return to the mempool and get mined into a later block — but the block reward for the orphaned solution evaporates.
Orphan vs. stale: a precise distinction
Strictly speaking, a true orphan in Bitcoin Core terminology was a block whose parent the node had not yet seen — an old concept from early clients. In modern usage, the block that loses a same-height race and gets dropped is more accurately a stale block, the result of a one-block reorg. Either way, the practical outcome for the miner is identical: the work was valid, the network rejected it, and there is no block subsidy or transaction fees to collect. This is why coinbase rewards cannot be spent until the block reaches a safe number of confirmations — pools typically wait 120 blocks of maturity before treating a reward as real, precisely because a young block could still be orphaned.
Why a home ASIC miner should care
For day-to-day mining the orphan rate on Bitcoin is very low — a fraction of a percent of blocks — so it rarely dents the economics of running an ASIC in a pool. But the concept is not academic if you run a Bitaxe or any rig in solo mining mode. When you solo-mine, you are betting on landing the entire reward yourself; if your block is the one orphaned, all-or-nothing becomes nothing. Choosing a node and pool endpoint with low latency, and keeping your own Bitcoin node well-connected, shrinks the propagation window that produces orphans in the first place.
Pool payout logic bakes this risk in directly. Under PPLNS accounting, orphaned blocks are simply not paid out — the pool only distributes rewards for blocks that survive to maturity. This also clears up a common confusion at the hardware level: the "stale shares" your miner reports in its dashboard are a related but separate idea. A stale share is work submitted against an old job after a new block already arrived (network latency can cause your locally accepted shares to be rejected by the pool). An orphan block, by contrast, is a full block that was valid network-wide yet still lost the chain race. Understanding both helps you read your dashboard honestly rather than blaming your firmware for losses that are really a function of network timing.
If you want to experience this race first-hand, our Bitaxe hub walks through low-power solo setups, and the gear in our miner catalogue covers everything from a single lottery node to a full home mining stack. Every layer you self-host — your own node, your own pool — is one more layer decentralized, and one more way to keep your blocks from being orphaned.
Related terms: Stale Block, Longest Chain Rule, Propagation Delay, Confirmations, Solo Mining, Block Reward