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-11-05T16:20:12.375Z
manifest sha256d71ab8345ba94ad2121aa677844ae1e3b865f6f2f8307cc2dc28a06b629841bb
html sha256a71236b3002a37dc14059f6bf41005be222c8a27e7b590a8258b57b184a73929
proof⛓ timestamped on-chain
txid996efb80ad1e963ce216ecf2bf83312d597e1c49ead68817550e69ef6cb84083
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 974,201 · 568 confirmations
SPV proof & how to re-verify it yourself
block height974201
block merkle root67883bacb8ff3825a7d70326678cfadfe015d8eef05623eaa3410777e8b8ca3c
tx index895
branch (12)4b2d5b30484d146a2a88335587844013054f5b347b1cb039f7bd11dfcb7470b8 12414bee9ac34bfcbfe5dff27002eb124fbcafcb41bc3b0dce94a894420772a4 d939c6454f8229982f919c0241b0e2a19cfaa313c38fbb917a6ec51276149d78 16b0568bc4eb27b34da87925908ae7d21f62f22ce538af36aebfd3f9a644951d 098570f25758cb0d3a95ae43b6d180a5e827658c896f140c86cbe925f87ee7f4 1cb97c98a3003c09c31d8b19f85ec535aeb657b9fea1ec08cda7c1cc40894cbb dee3e85bfdfe7fcfe4ab2fa99adba3da49d2762b9c88967db3ea153917815d8c d304b9f04fd9251de1d354c72249cf1b3335df1e924177e19d0f2cd4ea08ce13 7d6cc644a1c19038084a0e74ba1f8748c5c4d9d5cf92280214f2081de1b18d0f a925e8049cd87560bb762079ce670b4a9781f2ed37d88508d9fc2a9b3c282fda 53d1d57badb6abccf54a7e4f5f0d4eb4e24e18d31329a1f913344cf70c041ba2 d5be530cb7c10611023043eeb14ab9d3e0b2f3f46b4457d25771c9be3e870904

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