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

page snapshot

captured2026-08-24T20:20:12.928Z
manifest sha2561c51af6bbd62ef6b73e3ea98cc9db6bf2976a14d989b35b1569ab19a6b442121
screenshot sha256f617238a7a896f85764e68ee17fc22b85e34192cca11d3d123324d2e51d94b0d
html sha2566d60116770685c7b7572a8569864fd62675ed4c5fecece60ca6da3f3aefb50ff
proof⛓ timestamped on-chain
txid9f709551f49ec2cdc3b2bfdc9422c66d91b54f9a3d19575c7d29b10ea9434f36
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,756 · 11,013 confirmations
SPV proof & how to re-verify it yourself
block height963756
block merkle rootc1eb75413b571c3711bc37049f325d4bbc7feff39297bb92c7e4fdf8732e8a39
tx index415
branch (9)bc9f4b093c77fc68c0eca159e41923d4aaabba5782d35315849930b123c338b1 02fdfc8efc92704808f512090a7cfbfa96c0668bbf2e30f62c5b3a76089b767d 8ccd334168ac7fb5f0720d1f7c9d6d10dce39a0f6712fde77bf9bab9635e4329 ccc282f80516d6fee12b5fb7ed960a1dba65bbc5ea3fc205e9a4bbeeb816e296 ef5fd8c8068ccc4698bec4576278a7a7bfc67d23e025a77997b3dbd899089aaa 4cd4614776385f7b704d10ec10d69dfadf7a99cca2ad25c4e602405d1c0e4578 29f8dca322bed4d8bdaf449d16e828662811fe52b1fbd1e3d77239eec370fc6e fd403dbdb82f136e0083495a2e1de331c5ae541ca5cef35ebf31ee740a003b1a c417bbbdbbb0f238268cf9314dd913c613fc6720d759c7af30f89962965bbcad

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 963756 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.

⬇ screenshot (PNG) · page HTML · manifest JSON

Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 1c51af6bbd62ef6b73e3ea98cc9db6bf2976a14d989b35b1569ab19a6b442121; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 1c51af6bbd62ef6b73e3ea98cc9db6bf2976a14d989b35b1569ab19a6b442121, 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