Browse runtime blocks, application-ledger transactions, and validator activity. The explorer exposes public runtime state while preserving shielded-transfer privacy.
Live application state and user actions are enforced by the Express service and its PostgreSQL database. The Solidity contracts deployed to Sepolia are reference implementations, not the live runtime execution path.
The activity explorer indexes runtime blocks generated by the Express service and lists application-ledger transactions recorded for each block. Public transactions show sender address, recipient address, amount, and timestamp. Shielded transactions — those executed through the ZKP-216 privacy path — appear with existence metadata (block height, timestamp, transaction hash) but without amounts or counterparty addresses.
The explorer surfaces per-validator liveness data: registered validators, recent heartbeat submissions, Proof-of-Space-Time challenge responses, and slash events. Validator addresses are shown with their current active status, tier, and the number of missed proofs. This data is fully public — validator liveness and slash history are part of the transparent protocol accountability layer.
The explorer is designed to balance transparency with privacy. Public runtime state (blocks, validator activity, transaction counts) is visible. Shielded-transfer amounts, counterparty addresses, Merkle proof artifacts, and per-wallet balance histories are not exposed in the explorer API — not even in aggregated or pseudonymized form that could be correlated with other public data to re-identify shielded participants.
Live data snapshot
Chain Statistics