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-16T20:20:12.226Z
manifest sha256e4ceac9b323372b02304623d7f87589eeef4640a3b06df26ab44c1ec069fbdf8
screenshot sha2567e7c00d806858ab685ff2260269acde8ebb33afb4795486ebd6de2a75fb99bf1
html sha256443eef0b1af1de73ed440c2570cf912c16e0736dc5d80d5cd996fc9ce76a51fa
proof⛓ timestamped on-chain
txid108f924cb5382ae2e80a8304a9365ce73c6d082259dd487473e2f216393119f3
WhatsOnChain · Banana Blocks
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 e4ceac9b323372b02304623d7f87589eeef4640a3b06df26ab44c1ec069fbdf8; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / e4ceac9b323372b02304623d7f87589eeef4640a3b06df26ab44c1ec069fbdf8, 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