rbpi3
Live figures load here with JavaScript.
XL1 · XL1 Explorer
Every block as it lands, who made it, and how fast the chain is moving.
Connecting…
Waiting for the first figures.
Live blocks
Who is producing
Counted from the blocks Oxyon observed in the last hour. A name appears only where its operator agreed to be named; the address is always beside it. Who is who
Oxyon's producers · Mainnet and Sequence
Live figures load here with JavaScript.
Live figures load here with JavaScript.
Live figures load here with JavaScript.
Kept apart from the network figures above on purpose: these are our producers describing themselves, published as open data every few minutes. What each block pays, read from the block itself: block rewards. Where this work is heading: the XL1 Producer Observatory on the roadmap.
Evidence over assumption
Running producers means watching how blocks are actually won. Over a 293-height run on Sequence we found that when candidates for a height tie, the chain picks the newest one, because pending blocks are listed newest-first and the sort keeps that order. Arriving first is a disadvantage; arriving just after someone else wins.
We traced it to the code path, documented it, and reported it to XYO Network rather than exploiting it. It is the same discipline as everything else here: show the evidence, explain the reasoning, let others check.
Who built what
xl1-cli, the producer software — run unmodified, in a containerThe Raspberry Pi produces on Mainnet, where the reward balance is the traded XL1 asset and its dashboard can price it. The Windows host's main producer is on Sequence, XL1's test network: the balances earned there are not the traded asset, so that dashboard never converts them into money. What Sequence does show is real: who produced which block, how fast, and how the network decides.
The public dashboards only ever display an allow-listed projection of each producer's status. Nothing private — keys, hosts, internal addresses — is published, by construction rather than by care.