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-09-18T08:20:12.371Z
manifest sha256a469b431c6d90b360d3bbddc522852d7ba5a2907615ff94b8ea0cb5bc5264df8
html sha256d83ef0c9120de9897cbe3d42a20855cd0322ded29ae47bbadf22feab801f8894
proof⛓ timestamped on-chain
txidf25a839c5a0dee02a08438734f828155a6f91edfc773e1d68cda44dd8d82f409
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 967,281 · 7,488 confirmations
SPV proof & how to re-verify it yourself
block height967281
block merkle root6362491e8f3e11f94a56b953d13902c11fa0bc0c877fd9944c964297eefc4920
tx index408
branch (10)09d6e2e17d654d0926d57f0fb254cb1b885a5554f89fea2fecdbd7806ceefa59 f675a81a0c4f8ea9ebf0f6e7b691094669b39c466ea152a5042e1b0bf2af9f26 adc3d0ffed89e086d4e3f9c7088a7d65fac39b2dae1b2ef5a8f471855c7ecaa7 23221005fb9e56258bb7e0b7235e30b3111f9c2e3dfd659427424ebcc0dbe274 73e9db7ee9dd24be36d14f3eb2725d589c5222329f9a09dedcae3e891cdac7dd a60c2f4252314c7bdad124d518c9b0ffb895a4c815687057d02d225aa5abd321 db99f5305bac84b2fd3c9e84106958698cedd3225c16cfdd4ba52b65fb680931 1eae485e7cd40b0ff10d9d236d407b57abcd98e308388cd7de7c81d9daf13ea4 64195d4c9682cba30a65294d0e8fdae86759452a0c91d8ac1bc0b5db1e7b14e2 0e4ff1159d98dc96527fb64afd0ef602bd3a144031de2498504e0ced9b2a6a65

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 967281 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 a469b431c6d90b360d3bbddc522852d7ba5a2907615ff94b8ea0cb5bc5264df8; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / a469b431c6d90b360d3bbddc522852d7ba5a2907615ff94b8ea0cb5bc5264df8, 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