An orphan block is a validly-mined block that lost a chain race — two miners produced a block at the same height almost simultaneously, the network picked the other one, and yours got reorganised out. The miner gets nothing. Pearl has had 10 orphans tracked since we started watching, and Lord Of Pearls is the only explorer that recovers the miner address from the orphan's coinbase by parsing the raw block hex.
The miner most affected lately is prl1puv0gq…aqshKryptex Pool — they've had 3 blocks orphaned in the tracked window.
Two miners, on opposite sides of the world, find a valid block at the same height within ~50ms of each other. Both broadcast their block to the network. Half the network sees one first, half sees the other — the chain temporarily forks. The next block to be mined picks a side, and within a few seconds every node converges on the longer chain. The losing block is now an orphan.
Orphans aren't a bug. They're a natural consequence of physics — light takes ~70ms to cross the planet, and block-finding is a memoryless Poisson process, so very-near-simultaneous wins are inevitable. The orphan rate is a function of network propagation speed and block frequency, not miner correctness.
An orphaned block is a lost block reward. At the current ~2,845 PEARL per block, every orphan costs the miner roughly $X (depending on PEARL price). For solo miners on rented GPUs that already operate on tight margins, even one orphan per day swings profitability noticeably. Knowing your orphan rate is a debugging signal — if you're losing more than the network average, your gateway latency, peer connections, or template-fetch loop probably needs tuning.
The Pearl full node returns -32603: not in main chain when you ask for an orphan block via the standard getblock RPC at verbosities 1 or 2. So most explorers can't show you who mined an orphan.
Lord Of Pearls works around this: we fetch the raw block hex via getblock <hash> 0 (which DOES work for orphans), then locate the coinbase transaction by its unique prevout signature (32 zero bytes followed by 0xFFFFFFFF — appears exactly once per block, in the coinbase tx's vin0). From there we forward-parse just that single tx, send its hex back to decoderawtransaction, and read the miner's address from the first non-OP_RETURN output.
The result: every orphan block on Pearl now has its miner address attributed, even the ones from before we started running this code. The historical backfill walked through every existing orphan after deploy.
The dashboard home page shows the latest 3 orphans always-visible, with a "Show all" expander for the rest. New orphans appear within seconds of being detected. The full list refreshes every 5 seconds.