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-13T08:20:11.900Z
manifest sha2566229a2999e53138d5b141262db34c88cd996374c359dd693a4b951186e59aa40
screenshot sha256f4854c4db7bdc842c4962a49e72c140acc6a5af696adfb41065fb69772354340
html sha25696d88cd00f37adcac410b6bf933d7f54a19a5ff06922ea34ee184fef8ac61dc0
proof⛓ timestamped on-chain
txid5d8673e3ae5bb29f4a41fd9265e3566501ac3f81edb8852b2804ea445e3e3b7a
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,107 · 12,662 confirmations
SPV proof & how to re-verify it yourself
block height962107
block merkle root4eacea20da640571c75fa683be10af92bfe88e13cffd895aa43d634018628a4e
tx index119
branch (9)5a93dbd4f30e3a5593a17168a710e71afcac675cfe6606838df1e2054caa7e03 f0363ff57565c05f8be2ddb9c298f8aa4cfe19b22fb5045559b64b89cb2f733a dad099b8414209e192f5f4eb711aa7e0ded34aed5e7089044b3498ec50e42863 a577130195ffaa4e97049ebf7cf15a4e276dc1a0729a14490efb6381b6bd7789 9d304670b70035402ec7cf49c8c40e821bb5f3dad75fe475e1b719192017db32 c309eecd7b330c75587d331ee31e71daf37799073f89d177bf7dbccf07cf739a acfc92e9655b92380a86017fc4cdbc507b2a902c9db53142a70721f7cbdffdd3 e1eaf51585c8b229009c7b299d552aa1eae7515298c7bb2a2eb574c9c56c67dd 11d0cf6f3a811a983ee6fc191491d3be56a37fae22e350ac0fc5cb98451248c1

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 962107 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 6229a2999e53138d5b141262db34c88cd996374c359dd693a4b951186e59aa40; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 6229a2999e53138d5b141262db34c88cd996374c359dd693a4b951186e59aa40, 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