Live Status

Truth first — nothing on this page is faked, every value is dated

Chain data comes from the public Koios API, fetched server-side every 10 minutes into /data/chain.json (re-runnable by anyone). Node-internal data comes from a status file the TSUNAGI Preview producer publishes (/data/status.json) — the block-producing build, which is a different binary from the public follower download. If a value cannot be fetched, it says unavailable — never a stale number dressed up as live.

Network
…
Current tip (height)
…
Current slot
…
Current epoch
…
Canonical blocks (pool)
…
Latest canonical block
…
Live stake (pool)
…
Sigma (Koios-derived)
…
Node health
…
Producer build
…
Producer binary SHA-256
…
Uptime
…
Node tip (internal)
…
Latest forged block
…
Sigma (authoritative)
…
Next leader slot
…
Last leader slot
…
Connected peers
…
Parked serve connection
…
Opcert seq
…
Spawn failures
…
Peer disconnect churn
…
Intersect not-found
…
Panics
…

The producer build above is not the public download. The public Preview follower release (v2026.10.05, portable Linux x86-64) is a separately qualified binary with its own published SHA-256; the two checksums are intentionally different.

Guardian supervisor
…
Guardian incidents
…
KES key — days to expiry
…
KES period
…

KES expiry is a silent failure mode — an expired key stops forging with no error. This countdown is the predictive alert (warn ≤14d, critical ≤5d). Guardian (YAMORI/TATE) supervises the process; L1 not yet cut over.

Current canonical streak
…
Blocks last 24h
…
Blocks last 7d
…
First canonical block
…

Conversion-rate and orphan history live on the Blocks page — including the losses. The orphan ledger is published, not hidden.