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-03T12:20:12.256Z
manifest sha2569c4abf8c62aa6a2451c212273764682192f4dd1b01aea6806a3544038baefb4c
html sha256789a730d3da66df52e540991c1b3eae35b0dd7b83b6096f9de7b6cfe2054ea02
proof⛓ timestamped on-chain
txidcb6353c94c42521468fd4cfcd5aedcf0674ebc5c08cf6f84ca93c4358d134268
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 973,896 · 873 confirmations
SPV proof & how to re-verify it yourself
block height973896
block merkle rootb5c0597d2e1167e60a40f90addc31efc9f7c4d979509af4c7daa69449eac6c46
tx index1581
branch (11)e4621144a8347e92d816c3adb4ae91204ae517fd4dff86a3eea7f36318987a84 687603341553f02f2b0394ffbb5f2c700c7dea01c5fd81e043bfbf1ac69ed822 926cb16600b533d76f143a2259b58c7bebe826f9520413ffb73bd17eb6fef43a 18f8ac25dd5bdee72f6eec334f70de4993ebf51a1d7047318d9b9a29091a8392 2382d69875e9592e0fb7d6c0a3b9debb910547bc57fab4c3e8ee7b5335cc2774 a3049923ff7e81747a3189a67b342f99f96ac15cf521f9c8381ad38ebb08f0cc 8bd44226ae79f4467e6338911fd705be3af9d886aaff9711e21e2fdf28ac9519 780f787812c3a445cb89639ae40031ed50e630466367e11ddac1bba8caea2b3d 1f88bae89608bd2e54c3b9c5908697f2b15b87a54489be3ea11671e7269e9aae a32de48e0745e96334192f3e6fa544af2f29fbc65f1fd08863ad3eacbe0bc2ab b293266c4c5c03ed10ff2aaf957dbac27a52b24d6f3e780aad913130b266cc66

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