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-09T08:20:04.957Z
manifest sha25656286dccba8d15dd78cb0e10d3537b6c8bd3f86c61a4c38b259cd98807646e52
html sha256af566e402bee34d5252d2811cb3b5f4943580acf7e9bf6003ff34be0b695e13c
proof⛓ timestamped on-chain
txidc0c38943160cfc75e03ef1ee077ebc8a449813fa1366642ef3f5e72df4b9c6d8
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,962 · 8,807 confirmations
SPV proof & how to re-verify it yourself
block height965962
block merkle root3cf89e549ed0c7c673b2be8f5053adc63b0a726d42bacd7ea26318dba22103bf
tx index349
branch (10)2c90271036da7add53276e8028d9499721f8101d452ce21b1b7e84e7cb18f9df 5d1d9116c2b88096853ba0b3deeab588745823be0c4c397ab74705627b96bd64 08661a80685ed2cac34f27288ebafdca488422d4674fef5547fd42382d7af586 a30e80b54beeb4086f8716b1f30c16a1e1fa22ad64155ccc3cc78555ef2e3dca cfcd8e2847e74735dd1e63aa7f971b46bd90c021a91fcf75051183936c152f75 f05b535b44028ed48f39e09239fc77129be87a575490cf9b26018f75377fa049 70d825318b87c1b574f19d10c49002d49022b2c78f0a81afbdbab7f3784496ec 5cbade50473e4f4859a808f1296e9c17b9fa800b5a3419520884a1556c2ff2d4 9e1f1586982a0bf78742c2bc528cf957712325022b7d12e7f8c7a59236f69376 4ebfcf1ddc9486ad984b8d5832bdbfeec8e9fb61f5afd6cfc59032c4e32c95b2

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