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
captured2026-09-05T20:20:09.568Z
manifest sha256730cee34e08e772da20f9d673ae78f12a592ab63204172a838892986c6bb5494
html sha2562bd67d7b5ff03d99392e70125d10293a2e82ff5d7e3a6477b8e4b280dc618daf
proof⛓ timestamped on-chain
txid3bf503973399eb4c45cfd59e16af97746e72a50cfe3eab837f51ffac58992e00
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,481 · 9,288 confirmations
SPV proof & how to re-verify it yourself
block height965481
block merkle root1d22647864aadee96f6602e8840694cbaf670d7f3052fe22d2a476ff0f839f57
tx index153
branch (10)10a571ec89345146dfdfad1e5159b6f169c045b616f11167bf759e39d92b6b84 90c75e939f1bb3dced76384c930f4dada832c3a1044cc3286be5caffcf177bd7 c2d244f100dff2494588a3983fca16df2446ec87fd52a5f2490d410adbcd8a42 4e13b9bf2adaf743e0b38b19d2351ffcc66eba15033da71fffd4a23918c45010 091c9d49414055be97ec82a9e3db5e15a86635f462d2093cb25f646977d4154d 923c72a10b2f4e5306e9487f51c0a06160dde3b9f6b734294b6ab0473b473170 3266aefa8ee91f06b5e1c7eaaffdee462dabdd8a93bb22cdbf8ea75e4b9f2579 a902203282d4b94356bd413b45ef82a7ef47b8806c46c27573f94fcbd66f40ad 41909acc3155d98174f4098a0023f6ed250bfb681231b2ab988e154bf080434f 567a4d55bfc48fe7d3428adc27b7663d94d8a61ac701f5245f6c3290816ebd95

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