Web-page notarized

A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one

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-16T16:20:04.507Z
manifest sha256847ae8ccff61eddbe7d91a6c588d9e485461d03f186d37ab8d0ecd52b045bdb2
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha25660b93a46ff591f6966a1e326d68a9f962af61beb2e7775674458339d5492034a
proof⛓ timestamped on-chain
txidd23838527d904e3455c015fe2235fc8896d30a35c5c662a42dd27015f19f289e
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,596 · 12,173 confirmations
SPV proof & how to re-verify it yourself
block height962596
block merkle rootb69d73c04e31125b130aea58018e3f61f1a1536fc1bfd530c8450fb681e5ef24
tx index216
branch (9)201628782a52b1ed50d270ed7ef528aacae450e05ff6893dd7a78f261e7f7591 019e509d8c3a59985a0b24c51e262c4f8a963f3e8751b41f8ab55ed901af6b9b cbd62b627d6a0ca8324ee182d792dfc3e444a43f5979548379315d90e63b2c20 4e851f7e57b770c44358faddf755d7872cd3fbe9d8f12a13a2a8371f8d15dcc3 249d15fb8cff0bdc28c7f04ff167496aa990d0099ec86f2105e4d4dde4670d7c b46e4b5e8306650cebfee1e75b64fbc51099fd3bb5043d19b7164e6b3b0f326a 77be2cdb154d46e208147aa1196fd49a98fe4b380cfdd2f8f095f464ef7464e4 17edbc1b83f542b15109ab02c211ec70b9994be67ef2e0565c35f8c5037c5149 17735e2f209cc51da8beaa1cd2acee51479f80f3c3fc150b4010936b5744a911

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 962596 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 847ae8ccff61eddbe7d91a6c588d9e485461d03f186d37ab8d0ecd52b045bdb2; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 847ae8ccff61eddbe7d91a6c588d9e485461d03f186d37ab8d0ecd52b045bdb2, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (185)

← back to bsv.cx · JSON · saved HTML · ⚠ Report