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-18T04:20:08.051Z
manifest sha256e122af72e192d9d9002b875e0fd7fd74efe77d3c663903dd00dc1f89bc4e39bd
screenshot sha2567e7c00d806858ab685ff2260269acde8ebb33afb4795486ebd6de2a75fb99bf1
html sha256443eef0b1af1de73ed440c2570cf912c16e0736dc5d80d5cd996fc9ce76a51fa
proof⛓ timestamped on-chain
txidb9fab46fd3e7fd6cde0e58198473acb728a57d172e70800ca8aa16777fcc009a
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,800 · 11,969 confirmations
SPV proof & how to re-verify it yourself
block height962800
block merkle rootfd64c949217f7f4c99f37d764c649b78c2ba65c3feedc78f7e1a92052450b47e
tx index378
branch (10)df4225dcd0c71041ecaa6d6b8e7ca52f5b2279951f441d4fb4d5c1f8439aa8d0 fae5670fbcad63886a41be2ad13e098b5b28bff917b04e41ccfda86cc8aa4923 af09464071a16d93eaead7707d1b2c2e2472a86a2de8b90a653841c2b3b31147 d6d22efc3b5fe78cdd227e7257bbf60d12ade968b9151b27170397577f914cc3 1d3422899dfeab731f0fa5c0b609a94be26477ce73e566e34203bee923426e54 ef71cc3df3e152eefe032734dd90e4837427e20c93595a8258bd2b693dd8d20a 24396977dd884097ad62e951f1b40a1c905bb0c6fed42226995b6927919703ae f69150231ba35e6d28ad398b8958973a20cf135fa4159d5df73c0e35a63359e1 4a8f587acdb7fc0a8416aa1d046de2ea82bb1d73043bedf589f7a3da51af9e3b be8e8e295e3a28f4ce748b766c8b6b7ddeb5491dae518955c0389635fd6860b4

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