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-23T08:20:08.533Z
manifest sha256ae0a8f8e750f40a9582ef4aba1f4fe406b2d8586409a30fa448de85f1fde9dae
screenshot sha2567003a69ef1de6ed5ea5a99aa30a0aaa101a0f443cf0d876212b96bb99a398277
html sha256f0db594faeef1db896573b78809ee5ae9048f3bbc5cfd340e8faf85ffc44bf08
proof⛓ timestamped on-chain
txid358b996cab8f1a50bd01fbb781ee737dfd4a679d05700df48ffcbd2d63ca9cda
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,541 · 11,228 confirmations
SPV proof & how to re-verify it yourself
block height963541
block merkle root28fce0f147aece7be02fe640b6af6acb5fbcdb60fe7290054595f4b5b7fe7e04
tx index23
branch (11)e3a40318a360b5da765a2e238d472d4562364089b8bce8cf50bfa99bac7cb749 e539387fb70a3a176d78ac480b0480e3116b9d207b1d181f9a33726f7022a6d9 747d8b4b3eaec910d99c4f394b9235577e71c8db604333930cba77352c409613 9ab424e9761243bab2f5be3642cc55eaa2f6f9cede9ebe9facd23a46ad89c0b4 58046626490919db86350e94c8dfc512bb6b4eb58e34f8a8b7d80996169b5a84 fa56f7ededac703e051da6af8e4667f46001caa837da30040423919fc6e06951 da94bb8ebfe8096ba20ebc9e9f7dabf093ac7f714c6d5555c72cb70a0fffa508 1c4f4010f6e59c14ab3c48f779eb53bee01e4554053690ad6e71fa6b5a01d4ca 237fb27ff3ac4ce63dbadcdeedd8344ea8388c798ca6ea542781bc43ab5544c3 a2ac21fcc264827908b3ed64b017d5e327bbed24612903a666b9a2842ae07688 51c48cfc3934a910b9cb06a3228d95530b92f69119879de63f69b6a1c2778638

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