Web-page notarized

A tamper-evident timestamp of a page's content. Verify any proof — 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-11-08T00:20:10.527Z
manifest sha256b3d9b093a64b05fb8d7662a3093e15f3d272c168b99fea94bdb69a1f03b07fd5
html sha256f05480f0c5f1fe6c176f3904d5cb96f60d16eb0cace6de4bba00dad9ec9aea3b
proof⛓ timestamped on-chain
txid13a39895bfd080256a0b31ec4f0b2d4ddfa26388a55cb1bdedb96f4fc52468ec
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 974,538 · 231 confirmations
SPV proof & how to re-verify it yourself
block height974538
block merkle root768fa4f77dc055d3ead812b82953494fb79c25d85b8e8153aa2639263a77cdb1
tx index933
branch (10)808d06fafd52d1ace2789d484acec67efa47b54700e7724761dc0d4acfacb4f9 d7f11453d4d9138f8e6e5f203b9c16e141d95f599bf57933347e7ecb2d953861 ee1b08cb1ba0de0f19b6656aedccd5086f5a0f33283f73cb96d38757a19b0163 672829f974c422c8cb6b9147662157bbb4b8cabbc67852e80e1477c7e429bdcd 66a24ca6f68a7a520cee4b036c1faf667ad8b978fd3f3708ecd5403b78955bdc 2fbb796afa616baec7b762d0354250c51ef1666d3dcfe0cf1b41ee7829660b46 e2522688fc6caa5d19bb146a99217441c315f77a4d5bce0cd89d1eb4ab7a53f3 7ae934e3f9fdb54a6c6e130dd15e475cc8c9e15062992510bf621eb87a783e86 129fe150a08e33bc196c2e318498d8e565d137d59104443848d478f525780a7b c9689899693642ac28c9dcf4b562f4e73e1f5ab2348ece7e086cd3c838075672

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

Other captures of this URL (179)

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