Web-page notarized

A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one

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-09-08T08:20:05.558Z
manifest sha25668b8984727ec757556070b63e0595da044e71d8799c4487205486e22015e089a
html sha256af566e402bee34d5252d2811cb3b5f4943580acf7e9bf6003ff34be0b695e13c
proof⛓ timestamped on-chain
txidab118ea7b475863a956755e1f17772ce2dc1df6c124c738534646c8807ce3605
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,836 · 8,933 confirmations
SPV proof & how to re-verify it yourself
block height965836
block merkle roote54b56eac620cdc3080865e5aea1b8c274ec685ab125390553e315d897eb29ad
tx index62
branch (11)31f3dd7f8432abff345b8835714b589e20e92fcd03e4fd943d91ad060058befc 3a32c6e3faac92c6ec9df42148b64f1b9240172b1b35f92d74545696078e922e 9f0b61ce1c448616889c61bb06459a3645b78440a0ae71be5e4d6f12baec4e3c 2ed6f5323490cebfbed024b099487a64969651c5eceb2c32c4a1f26f3839eef4 a0fc62bf54f2904ef7223fc130d9d8165859db20fbd212e1ce920e122c2d4ebe 6098d9ed6afb8345d03e9566008742bdf541b4f4a972a9edd46d8f5b767bf11a 8b2b52ac807343f4626a07ac7049e3bbfff493e9617dadea45e027e9b49409f0 2c924047ef4cc9e3aa94ccc793415935b8dbe4aacdab48eddff62fa4671bd492 812855b9df9c415be5bb95bbe689f3c10d5580166d32dc82b96bdd407046579e 4d6bfceb7f11a1f8c66bbeb780e6214a75ebe3a78f27e477978ca19a34d1bb38 5f44f7e3ec07a17432585b44ef8a1cd6236ebd7a9beab118dc71faafa6fabeec

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 965836 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 68b8984727ec757556070b63e0595da044e71d8799c4487205486e22015e089a; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / 68b8984727ec757556070b63e0595da044e71d8799c4487205486e22015e089a, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (185)

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