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-23T12:20:13.240Z
manifest sha256152832cf00fb30ada71dfaf5220114761c95968a214c716f4c43bfa367c24c9c
screenshot sha2567003a69ef1de6ed5ea5a99aa30a0aaa101a0f443cf0d876212b96bb99a398277
html sha256f0db594faeef1db896573b78809ee5ae9048f3bbc5cfd340e8faf85ffc44bf08
proof⛓ timestamped on-chain
txidf8748f2094dff9f62a9d005e6eea0e2110f1be5202e7e1db281e487cde13bc2c
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,562 · 11,207 confirmations
SPV proof & how to re-verify it yourself
block height963562
block merkle rootc15b706eb442906a629e40395b831d9956b874bc2fd41b2f79ee4a4c06f99874
tx index235
branch (9)616962dbfb128a37c7a09396f45d624634a0f4b90088459b317e2e22486f9743 e879234947d6842b1704e76a2829b3c0d98371356af3032e76943304960ff8fc 4b26128c571bee7b0c509aed49b28231247e27e08163ddc1d507ada5b2e9c3c5 3d8c463683afc7a9a16c081169c666c45da8ab898b4f7398d6d4a31a0d963fdd 633e69e350d9072af9a9ac00c812af1ab2d6d94415a38c5a1729063024761251 51a1b3c72e74906c33bc3946287d4f292ade18abee9d97de9079a408adbfd426 2bf4325499ad5a66d367acc331cf07b13ab301b7e39f711db57e886569c3466b 2311eb68ba4d84f1ec9104a9f60295ce6e86ef860cd85b156cdc6201f8e9e816 f1f57766304cd63d38be6187a9b7a1b134106488cceac2c3ecd780550d7b1c84

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