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

page snapshot

captured2026-08-20T12:20:12.995Z
manifest sha2563a9531501f668deb7f496e828d2fee40206ca7e855baf0545bb8b0849367204e
screenshot sha256d4689d5f97c4b66ba609252d947c9d19e6934a8268176ca0bd2deb87035fb732
html sha25648776d9828adecf3f5bf8abfa42d5577a0ee1f112809380a2041066a20d8c2b9
proof⛓ timestamped on-chain
txid19bc3ae103128b09f5f621b1cf916e9b21303f171f48d1ef6e3f4ee419d1d758
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,145 · 11,624 confirmations
SPV proof & how to re-verify it yourself
block height963145
block merkle root0620ba4b5433256db22646775c18ca94f89ebdb8a042eac36c80f4b59be336ac
tx index118
branch (9)aa23be2248ddf6e96b542eb60569d9eca6f30e4d1817f9e9f4efc682e01705a4 4f4c8a7a653dfb4ee990a0a3a15de111fe4d772ead9b41d434bc70c994a03942 78a32894dcba6fae0efce8108c3cb4a5b8d052e31dad08788a9d23c1a3180d83 7c1f29d064f21e7835575029fed66c80394cb25627c308dc6db22f96714d4ef0 68d94d057c4a765bb18a1b532baa4a19d9dbf7a1be34c6050f7c27c30e9daa30 58b2a8a4bf57b27fc07610f48e6ba15404184c6df35c7c0307bf3edfde9a23a2 e06317dbef3e5f04bee95469c368b4655a3b421f4d6a738d8db36669b968912f 05a83d2d48de68209284e90c15370fe4f967b31f77258939d7378cc5c711990a ba1bcd1dcc9386e5e125f69398ff9583422b1091783c6393477027252effe81c

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