Is this document anchored?

Drop a file you received – a statement, a white paper, a decision – and the explorer tells you whether its fingerprint is anchored on the network, since when and in which block. The file is hashed in your browser and never leaves your device.

Drop a file here

or click to choose one · PDF, JSON, any file · nothing is uploaded

or paste a hash

—

How it works

Your browser computes two fingerprints of the file: SHA-256 and keccak256. Only these 32-byte values are sent to the explorer.
The explorer looks both up in the GenesisAuditAnchor contract. A match returns the anchor number, record type, writer and block.
The block carries the validators’ signatures – open it to see who sealed the record and when.
No match means the network has never anchored this exact file. A single changed byte changes the fingerprint.

Registered governing documents

Try it with a daily statement PDF or the sealed snapshot from the statement page – both are anchored byte for byte. Daily statements and snapshots are anchored by SHA-256; control-plane records by the hash their producer used. Both are checked.