Explorer

The proof of Bitcoin's history as it stands right now, the work in progress, and who is doing it.

The board restarted on Hazync v2 on 12 November 2026 and is proving the chain again from genesis. Hazync v1's proofs are kept as the record.

The genesis proof

…

One proof that every block from the genesis block to here is valid under Bitcoin Core's own consensus code.

Proved blocks are joined into it afterwards, by provers who choose to do that job, so it can trail the number of blocks proved.

Unspent coins after the last block: …
Total work, from genesis: …
Proof size: …
Last extended: …

Hash of the last block

…

Unbroken from block 1 to: …
Chain tip: …
In the genesis proof: …
Being proven now: …
Provers: …

From proven blocks to one proofEach stage is measured against the one before it

Proven…

Anchored…

The genesis proof…

Being proven now

Blocks a prover has claimed and not yet submitted a proof for.

Prover	Blocks	Lowest	Oldest claim
Loading…

Recent work

The latest proofs the coordinator has checked and accepted.

What was done	Prover	When
Loading…

Provers

The eight with the most blocks proven. Each prover signs its work with its own key, and the coordinator checks every proof before it counts. Select a name to see everything that prover has done.

Top eight by blocks proven
Prover	Key	Version	Blocks proven	Folds	Anchors
Loading…

See all provers

Check a proof yourself

In this browser, or on your own machine. Either way nothing about the check depends on us.

In this browser

The verifier from the latest Hazync release, compiled to WebAssembly. The proof is checked on this device and nothing is sent anywhere. 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.

Check a proof file you have

On the command line

A 2 MB verifier from the latest release, for Linux on x86-64. No node, no chain data, no GPU.

curl -fLO https://github.com/hazync/hazync/releases/latest/download/hazync-verify-x86_64-linux-gnu
chmod +x hazync-verify-x86_64-linux-gnu
curl -fLOJ https://api.hazync.org/api/spine/proof     # lands as hazync-spine-1-<N>.hzk
./hazync-verify-x86_64-linux-gnu --network mainnet --product hazync-spine-1-*.hzk

A good proof ends SWIFTSYNC_VERIFY_OK, or, while the proof is still below the amount of work Bitcoin Core pins, SWIFTSYNC_VERIFY_DEMO: … a valid chain from genesis with the tip it reached, and exit code 2. That is the normal result for now, not a failure: compare that block hash with any explorer, or pass --bitcoin-cli to check it against your own node. A proof that does not start at genesis is refused. An aarch64 build is in the same release. The program IDs every proof is checked against, and the API behind this page, are on the developers page.