Web-page notarized

A tamper-evident timestamp of a page's content. Pay-per-call — bsv.cx

Rendered page — archived HTML, sandboxed · click to collapse

Html-only render: no scripts or original assets, so it may look unstyled. Not the live page; not endorsed by bsv.cx. ⤢ full screen

off by default; remembered for future views
captured2026-10-02T08:20:13.040Z
manifest sha2563c68a19a9a2ee9b00483fa936711b5b38c4f3d75eef47d835c944649a1d3750a
html sha256f328f9c44a91b44cd72b540fdcf81d30a3dd1c7b059fe9516d690822642037b7
proof⛓ timestamped on-chain
txid3128622abd135bee26707aefe48a90c2b5f7f952420671b2245c4b7ba7cb7fd4
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 969,299 · 5,470 confirmations
SPV proof & how to re-verify it yourself
block height969299
block merkle roota899ff56e0a7b8a796a286c1d969c928a79022b84f44eb591b64d888ff542f1e
tx index154
branch (10)bcf779e1659923046788ddc63f2ac6517dae342ac3c387ea7f4d9462489ac0a2 3c8fec95c9335e927597380ad65db1c71513fab89cd649998682d3f001b7d412 3f2e6c5121d175e6603e14902aa513936b56ea11d405c91a2037efe27c5ae091 1d52f8bb6c37fca403b34550304948463ae4c02edb7e42e35fd3814442778666 e677f9ec4a18c0d8be39455dec0bea910fafe1e9c61414994188d6e82c29395b 91ea0eb3068cb34a2965a4b01f5fb29200b58f66325f68f6fe89ad2758c83bc2 a72f2ba3cb1bfca678fc1dd35528d07c157e676453087252fdf4f0e8f74d026d 0b0a6fecc0e6dd0a3f11730851e4e9f7a7c31a32c959817db227b77a186883c7 32e12273ec41ad5dc03e9b139141aa492461a3d8fc3025e63c3cba20c6cb9ee1 d92928f3d307ba33bc6591c32cc3ccdea7ded62262d7d0bc4270baaf77a4301f

Trust no one: double-SHA256 the txid up this branch — at each level your hash goes left when index is even, right when odd, halving the index each step — to get the block Merkle root, then confirm that root is the header at height 969299 on any block-header source you trust. We verified it against headers we run ourselves; you verify against yours — no explorer, and no bsv.cx, in the trust path.

Prefer to check it against a second independent source? Paste these fields into our public verifier (POST /spv/verify) — it folds the root itself and checks it against headers we sync, so it can only ever make a bad proof fail.

Or take it to your own tools in the ecosystem standard format: BEEF (BRC-62, tx + proof) · BUMP (BRC-74, path only). Any @bsv/sdk client verifies these with no bsv.cx-specific code — Transaction.fromHexBEEF(hex).

keep your copybsv.cx stores this snapshot as a convenience and does not guarantee to host it forever. Download your own copy now — with it you can prove this timestamp yourself, indefinitely, without depending on us.

⬇ page HTML · manifest JSON

Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — so from your saved files you can recompute every hash and match the transaction's OP_RETURN yourself, with no dependence on bsv.cx ever being online.

Verify it yourself: the manifest is the exact JSON whose SHA-256 is 3c68a19a9a2ee9b00483fa936711b5b38c4f3d75eef47d835c944649a1d3750a; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / 3c68a19a9a2ee9b00483fa936711b5b38c4f3d75eef47d835c944649a1d3750a, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (600)

← back to bsv.cx · JSON · saved HTML · ⚠ Report