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-14T12:20:11.959Z
manifest sha25665bd0b40ca6c40a1028cc2af10c041ed7a55258a72cdbed3c20e248986746371
screenshot sha256c2c15beb5af101dd726d2e9532892e0bef416906ab13d0f4c83510bf72fa0531
html sha256dbe184f73d27d582d36a76ccf945307bfcfdb0f37ff8797f10f58f432066d6e1
proof⛓ timestamped on-chain
txid5f052d0839b473d835778c097d24e56cb51cbf8a1020941e76bbe7bca9ea551d
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,278 · 12,491 confirmations
SPV proof & how to re-verify it yourself
block height962278
block merkle root2ce7c36d807d629a456569ad6b4d2e9ca411fbe300b00e31ac451d86d2bddbbc
tx index247
branch (9)a2445e06fac41634e2f182196631073cefa43d1279229ee82563348d133d4835 afeda46e09268d02f1e977055b57eb80ac83dd59b8681256f5e0a80bebf795ce 3a88a1b9dbfc05835f879699078f6323d896a45dbe5f0b27fc1641ce5726458f 9391acf3182c5047b24e95ddec7d058c921c12b503149e5fe449afbbae32a557 5eb25a9f878bfd8c76ac191d54369104c725b0ea3d55c8f2c0a21eaedd0c34e6 992e01476457a1895d8db1146431eb3f9709708a670f006e23ae0a301bef186e d41c20b1825d6957f606ae6fbe92267886aff23b8289adce1490f71049014761 845c3ca17decd44a5dbdfb57867b86f8ae69b04ab444deec2d584018a9660f3e 42e135962772a3232974cb2684234d2b33607ebf8cf51c05330b7b4addfac0db

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