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
captured2026-09-08T12:20:05.065Z
manifest sha25678671ebb457c1add5b2dd89800a9c3a1a4c1868a58bff35951d992eff0878681
html sha256af566e402bee34d5252d2811cb3b5f4943580acf7e9bf6003ff34be0b695e13c
proof⛓ timestamped on-chain
txidb5aade4c37609364ccca09650e79e332a835a23438f012c5d4b25c691028a472
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,859 · 8,910 confirmations
SPV proof & how to re-verify it yourself
block height965859
block merkle rootab348479d483d5c4ad571bcd117c11f7a05de49eda466da70cffd63d3c0f7437
tx index821
branch (11)ca26809abb0dd73b3ded00eb3cab50ea327ba59c0aa28a277c7bad8d6371f6ff d21e3fc3bd8e6c93988312fb1f934784fbdf961e0e6429c0979001981d36bedf 79d347c5142d22b45112bbd5a20fb208cc838af8f15d22c35e8b651dca75098c 08cddcb1c17133f2f8c22c796d93b4110f84ebf6afab1ac56c9019bb0d03527e e79083ba3d2001185568067673b06f274b448e08a60e481af0e8da7127653324 f743bbd6dea2eec7a4b948463a9b0d15927f1ad6fa9c3e3131006165f34a24ba 31c0f40486168ea7a3383ce6d148212a4f713af3bf281f65106dece592de67e8 5f415db9df8efc2327d52d99108d1410c2e4ba40a85484b5478cf6b714fb242c 90bee833363b81bdb85a4d96be0c6fa1ec6a4c905bf3067e845a9ae09b0a8920 b36215618cecd53bb1bdf67af91ed26cb1828c5ed10509b271e83233fd58300d 87dae176bab870f252cb61d583bb6dda3a6b5be9884243497d283549ec419d5a

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