Web-page notarized

A tamper-evident timestamp of a page's content. Verify any proof — bsv.cx

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-12T08:20:08.224Z
manifest sha256467b1a964112161732a6d8656094a718bdedd27fde9efc1041ee17d63755c28d
screenshot sha25662cd048f3a081d1cd131b452970551e38119bd6493e1653d88dbd2715c032b02
html sha256db7679bc5553ca5c8672ecf1b10fca87e3dd1189e1e928abd5b9d465d72e6a4d
proof⛓ timestamped on-chain
txid4f3286d0289258ade3438ab14d91e5a93942b94752e6a5c63cd2721633bf4fcc
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 961,973 · 12,796 confirmations
SPV proof & how to re-verify it yourself
block height961973
block merkle root203b2d83a91b907d7fe72ead3c4a43c30ad365424c4119f85e09e39bd55f8ae8
tx index281
branch (9)ce0b369b1a5a1a72d946beed7061467861fcf696492ad5037efbc53f2883e7c0 de929bc16590767e4691c3cdda8838e8414d720e7e27afe5363d9efcbcab03f8 702672c0ddc1f4067458ee8406442cafab21166a1b5d641060a4ec132f0a2e8e 014a55db1909ec082c956c46fb0ce2fc80de590eb5925a0cd22ddbffd994ff15 7cbec9f19a0350c20f86c4644909a2f0160046eb2166e2b6610e8db2da7adca0 48c3da990d3d93dcee6340ec7fc6424f0b284a623b05bc9cf08320e5e59ce26d 4938ae84f783d127a1d9dfcf2f0343b0e430a7d1e58c006f97eba9a5eba032d1 67631e8dc70e3d97e74a3f70646a3390bf15336be5033772685ddf03b19602d6 7ccf3f1b8ffdb2e3603a3469c7dd8bb82a98e6d984f0260f6929d0c68c54b054

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

Other captures of this URL (179)

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