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

page snapshot

captured2026-08-16T08:20:07.991Z
manifest sha2563ec2c43fd2c9190ce9ba7a4127159a12bbe4be4153c72d5a8bd2915d22bd85b8
screenshot sha2567e7c00d806858ab685ff2260269acde8ebb33afb4795486ebd6de2a75fb99bf1
html sha256443eef0b1af1de73ed440c2570cf912c16e0736dc5d80d5cd996fc9ce76a51fa
proof⛓ timestamped on-chain
txid1fed475557f33d2925f2a11c39542dfaeed49c6715f55cda3cdc38483706484d
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,550 · 12,219 confirmations
SPV proof & how to re-verify it yourself
block height962550
block merkle rootb32d21e69cba2ba455b0bcfa86d673060d5c6e8a0ab616aa4ae70fd750149c64
tx index3
branch (5)5a447f13cc9ed202b3315404dc33e2456a4096dd5257a0d98f7dcd82622fdc96 2d02f280cd88c94bb1c0cc2fcea9efa95b9cce8660b0b6fe788105d29eace12b 90e14bf2c907d9c186ed2aa7fe2f67ef8ed5f8bc6a9387a22046d64077b87bd6 f00d0e7e36d2c928ccb9d10b6742747c18fd5238aef2dc77d6b08f6f16c1112e ee0cd567da4e008f55dfd52d78a8530079d833619e334670067035f39ea58323

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