An orphan (often discussed as an “orphan block”) is a valid block that is not included in a blockchain’s main, accepted history. In practice, this typically happens when two miners or validators produce competing blocks around the same time, or when a node receives a block whose parent is not yet known to it.
How orphan blocks happen
Blockchains are distributed networks, so blocks do not reach every node simultaneously. If two miners find a block at nearly the same moment, the network can temporarily split into two competing tips. Nodes will follow the branch they saw first, until a subsequent block extends one branch and gives it more accumulated work, or “more proof,” than the other. The chain-selection rule (such as the longest chain or most total work in Proof of Work systems) causes the network to converge on a single history.
The block on the losing branch becomes an orphan in the everyday sense: it was valid, but it is not part of the preferred chain after consensus resolves the tie.
Orphan vs stale, and related concepts
Some sources use “orphan” to mean a block whose parent is unknown to the receiving node, making immediate validation impossible. Once the missing parent arrives, the block can be connected and may no longer be “orphaned.” In many crypto discussions, however, “orphan” and “stale” are used interchangeably to describe blocks that lose the race and are discarded from the main chain.
A real-world example is Bitcoin, where short-lived forks occur naturally due to propagation delays. In other networks, similar events exist with different terminology, such as Ethereum’s historical “uncle” blocks.
Orphan blocks matter because they affect confirmation confidence, miner rewards, and the security assumptions behind finality, highlighting how networks resolve disagreement and converge on one shared ledger.