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-26T04:20:08.767Z
manifest sha256d39d48146817ccd4638ff3746615264b7dbc0c2ca976bd0f7b5901bcfff5bb1c
screenshot sha2567690736f43eed0a92070907fdee2935e239d53f88c9bc371df15ab38672c517d
html sha256b0ff0476379251b5679c888e42cbee84e22b433611fc81ddfef98a8a736716ce
proof⛓ timestamped on-chain
txid65b62b6a578399239c82b46cd45410809bbff21059c1f54ec7af3a401625a956
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,944 · 10,825 confirmations
SPV proof & how to re-verify it yourself
block height963944
block merkle root16545f4610051e867d93589f0db11598864117647d3f34bb6c6e37e7687854d8
tx index31
branch (9)4b08d23f505155fc555e01f34de5d4412a12004a9b1f5d54194c8e63e6441b46 1c76db8320c83c9683944de32a3631b168d5699e27e858a3d8b71e67051332a4 f6d8624bcf2b26f4c297ff6820fd1d4c82892ce991228e6fa8bfa14d5f0f3d44 aa104510af75f18fdc6b7388474ffd956936d0ccb12fe62e01182e6f2bfc297e f9975ea46efc4f2fb82de852a47f3e65abb0f025e3a804a315e84582affe85d3 a00fef9b0382ae05f7b3edd477b6185ff0ad18ee5f61644a46d8ab1e975f77d2 275c31f38f4c2638235a5a2e5d9a903a55fd17cfe6b294ef692dae740bcc9063 719655f6f0b13f345246a5fc4a148864975daa74bab634530fbf2fcfadc43412 465bb2456bb770ebd3588ddec5021ed87015acd1311610b3a4f8f74506554efc

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