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-24T12:20:12.284Z
manifest sha2564f33732d9a2fa199c595095cfc83f4cb692f5bee0159276e4d56526000166a9e
screenshot sha2567003a69ef1de6ed5ea5a99aa30a0aaa101a0f443cf0d876212b96bb99a398277
html sha256f0db594faeef1db896573b78809ee5ae9048f3bbc5cfd340e8faf85ffc44bf08
proof⛓ timestamped on-chain
txid1dcff66a6c588fb34e74c6339544d91b2bc733c6379839f7dcda5ea45a39529c
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,704 · 11,065 confirmations
SPV proof & how to re-verify it yourself
block height963704
block merkle root91ddd5a9dc3cb173b2dd1ad9670218b12d2e135206772923b73c74a93087d2d6
tx index12
branch (5)054a248e526ff2d528bd09a92ee4681a3a5b38ea942718d371252af228268ab0 a75764a594802fec23d13d804307135abe637775afde74de5c93f026305e4604 61daf8a5356618778784f2a4a9f34beb5149a22a83024b2ed71e39ff4dca811e 4fafe67b91166bfa5dbf1d7d73c9d721de205333d79288d0eeddbe8ebfceaca2 db8c0357d0d87cbd41956549ae2ec6f3cff4c30ef7626caec0c5caaee9b43256

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