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-17T04:20:04.879Z
manifest sha256811f2bcf5dc8e22934ab43a969a8d6adf25c45f168cf5cc058c464c64b834479
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha25660b93a46ff591f6966a1e326d68a9f962af61beb2e7775674458339d5492034a
proof⛓ timestamped on-chain
txideec0362dcb52991f46621a12928a36b8db2843f2b0cc2ab3392c050899a45e07
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,675 · 12,094 confirmations
SPV proof & how to re-verify it yourself
block height962675
block merkle root52996e705779be0254611837f19d54299f92770cb2b9c4ecee15be3dec0e9a37
tx index142
branch (10)3b2d79975e5cf87cf38b22da33d3599a878b1f24eaba86289c05e85a86ae3f68 42b45939bfb4b5b11e81b480955b79344767138e2d44830e847be85dc0ee8e04 b9b71f61bc970e0e9e05b0e682cdba2d717cb9c833da83eb9ff9908b96c5ad50 d9f8a016b52f3c13681eed5c399d56346fa7ca9ec5a692992a22abe3f54dded7 18032f8d708c2f3898c958c532b4e04a6f6d8c111f79f4cbbe136dc453c6f93b 4b33b0c6d8d66572d0c5f48f5e63326415fcd906af1c41298ec1b56cdd69fed2 d9ccdb05dff786b4e95d2bccec292f806827080016b4d57b9e7e25016c4db845 4d5962fb451d2d8fe83e82855c13654b6dec21e4f07a6396844e9015a21e7263 791671f668bbacf04be28163569baad567e3d44f2c01b4d0945131696b1d8c79 4af75f79f191de58695116bbbd44c7e74e7c31f44fcee0ecb98f67c347175d0c

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