hazync

Explorer

Every block the proof party has proven, who proved it, and the proof itself. Pick a block and check its proof here, on your own device.

The chain

  • Proven and joined to genesis
  • Proven, not yet joined
  • Being proven now
  • Not yet proven

Select any part of the chain to look up the first block in it.

Close up

The whole chain is too long to show the proven stretch in detail, so here it is on its own. The genesis proof is the single proof you can check in one step; blocks beyond it are joined to genesis through the coordinator's unbroken run of proofs.

Blocks proven
Joined to genesis, up to block
Single genesis proof reaches
Provers
Last proof submitted

Check a proof in your browser

Nothing is sent anywhere. The proof is downloaded and checked on this device.

The checking is done by the verifier from Hazync release v0.21.0, compiled to WebAssembly. It confirms the proof was made by the published prover program, that it starts at the genesis block, and reads out where the chain stood at its last block.

Recent proofs

The latest work the coordinator has checked and accepted.

What was provenProverWhen
Loading…

Provers

Each prover signs its work with its own key. The coordinator checks every proof before it counts.

ProverKeyBlocks proven
Loading…

What the proofs are checked against

If any of these change, every proof above stops verifying.

Prover program ID
A hash of the exact program that proves blocks. Rebuild it yourself with the reproducible build and you should get the same value.
Browser verifier, SHA-256
cdd84c38d9b21d2b93fc1f86b5a933b2e96f14cec51ffb7f4de9746278eb30c7
Matches hazync-verify.wasm in the v0.21.0 release.
Coordinator source, SHA-256
Reported by the running coordinator, so you can compare it with coordinator/server.py in the repository.

Earlier program IDs

Any change to the prover program changes its ID, and proofs made under an old ID do not verify under the new one. So each change restarts the board from genesis.

Program IDFromWhat changed
37987b85…6 Sep 2026The Core build becomes the one that ships (v0.21.0). Current.
3867611d…4 Sep 2026Faster field arithmetic beneath libsecp256k1
1d6c3792…23 Aug 2026Parallel block validation
b62d2a60…4 Aug 2026Guards from the fifth audit round
dfc9eeda…3 Aug 2026BIP30 closed with a coinbase-only Merkle tree

Older IDs, back to July 2026, and the reason for each are recorded in reproduce/METHOD_ID. Proofs from earlier boards are archived and still verify with the release that made them.

For developers

Everything on this page comes from a public, read-only API. Use it for your own tools.

GETReturns
/api/state?slim=1Progress, recent proofs, provers, claims and the chain timeline
/api/metaProver program ID, frontier, coordinator source hash
/api/vrangesEvery verified range, each with a link to its proof
/api/spineDetails of the single genesis proof
/api/spine/proofThe genesis proof itself, as binary
/api/proof/<lo>-<hi>The proof for one range, as binary; /api/proof/<n> for one block
curl -s https://hazync.org/api/meta
curl -so genesis.bin https://hazync.org/api/spine/proof

Hashes from the coordinator are in Bitcoin's internal byte order; reverse them to compare with a block explorer. Proofs check with hazync-verify from the latest release, or with the browser verifier on this page.