Ledger Explorer
Every accepted telemetry record is hashed and committed to an append-only, hash-chained block. This page reads the live ledger. Anchor state is shown per block exactly as recorded, with no claim beyond it.
- Committed count
- none yet
- Batches received
- 1,217
- Difference
- n/a
- Signature verified
- n/a
- Received at
- n/a
- Chain head
- n/a
- Committed count
- 69,065
- Batches received
- 69,065
- Difference
- 0
- Signature verified
- yes (ML-DSA-65)
- Received at
- 2026-10-05 23:10:04 UTC
- Chain head
- bf48e0b1aac97e76bb0563203f0e1beeeb61065af1fabd62d15d62dca902f01f
- Committed count
- 69,405
- Batches received
- 69,405
- Difference
- 0
- Signature verified
- yes (ML-DSA-65)
- Received at
- 2026-10-05 23:10:05 UTC
- Chain head
- 1818803f901d75478d494149c2afe7c5a410e4b6771a787eb4ffe18a0b3119cf
Last reconciliation applied 2026-10-06 04:25:08 UTC. Reconciliation runs daily and compares each node’s own signed submission count against the number of distinct telemetry batches this service received from it, deduplicated on the batch payload digest. Known non-ingest chain entries, such as a node self-test, submissions predating batch-level accounting, accepted submissions whose accounting row was lost to a since-fixed unawaited write, and submissions this service accepted that a node’s local chain never recorded during a node-side restart are carried as a documented per-node offset.
What this shows, and what it does not
A block commits a fixed set of telemetry records through a SHA-256 Merkle root, so any later edit to a committed record changes the root and breaks the block hash. Each block also carries the previous block hash, so removing or reordering a record invalidates every block after it. A confirmed Bitcoin anchor adds evidence the operator would have to break a third party to forge: that the block hash existed at a given time, checkable against the public timechain rather than against us. Anchors that are still pending show nothing yet, and are labelled as pending.
This is tamper-evidence over what was published. It says nothing about whether the data submitted before sealing was accurate, whether a node was compromised, whether something was never submitted, or how events and methodology are decided. Verify a record yourself.