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-26T04:20:12.315Z
manifest sha25693491329fe15cfb747aa20d5404abe372580ba051545dc2808eb2fa2ebfe18b7
screenshot sha2567003a69ef1de6ed5ea5a99aa30a0aaa101a0f443cf0d876212b96bb99a398277
html sha256f0db594faeef1db896573b78809ee5ae9048f3bbc5cfd340e8faf85ffc44bf08
proof⛓ timestamped on-chain
txid7be6df0b8020e16a7657ee9ffdf55cf9f9a2ef423aac787645133c5f8b83ced8
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,944 · 10,825 confirmations
SPV proof & how to re-verify it yourself
block height963944
block merkle root16545f4610051e867d93589f0db11598864117647d3f34bb6c6e37e7687854d8
tx index33
branch (9)289f03d09163e3f60f8b342904f8c44b1644cb4d268948d11dfc5e5a96641d6d 16b3b25030dfcf4405f264695b93d8c821cc41aab30bb61f1c8ea4b6589c44b8 b9fcc3b334ece7e4cc8175c11ae51b542bc65dd6464d7b669b79d899f709d45d bde335aeedfe7f17b06d1868f339fa7d3d542afc59776e3417cb643731de7ccf a10cfdafab49e2a9040ac11884642aa9ab1a86843ddb3f2669881b4ee01299cf 7a1e215ce6a2549f10938c09e84448f5b42e571099a017feba594ee74eddedcb 275c31f38f4c2638235a5a2e5d9a903a55fd17cfe6b294ef692dae740bcc9063 719655f6f0b13f345246a5fc4a148864975daa74bab634530fbf2fcfadc43412 465bb2456bb770ebd3588ddec5021ed87015acd1311610b3a4f8f74506554efc

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