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-18T12:20:09.375Z
manifest sha256b205d9f9f3050b4ce70fb05bebf9979429a4a8f78b14682b3bb31a7bee3a5373
screenshot sha2567e7c00d806858ab685ff2260269acde8ebb33afb4795486ebd6de2a75fb99bf1
html sha256443eef0b1af1de73ed440c2570cf912c16e0736dc5d80d5cd996fc9ce76a51fa
proof⛓ timestamped on-chain
txid689adc22b17697325632500af05067bb8e8fe37d149027fd35ecd3d178517dca
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,855 · 11,914 confirmations
SPV proof & how to re-verify it yourself
block height962855
block merkle root8c090eee134f7bab64598450642ac4e8d7245178da667ef7facd5e148df3092c
tx index951
branch (12)81fd9eec88d32719f1a7b7e8a552616c9f5119be86af96e7173727564dd7dac2 05aed26a78724e23ce0417a627da89d41994f3ff0ba7b307d63fc578f8a71789 c2cf94f882ab0f533707a0c17d297d477573605f8facc75328e82fd47d7f0f7b 5e9a75a03031f9368b1d322b8baec4679280956cdae7cea0995dba2857d275c1 e8d8b53b2cb71ff4d77eb7040ea514e5fb04dff680ca4d6a3e6182e3ffc4ad3b ac4d21890dcb506ac18648ce01cbee09dcb772c6d28e3f7be16489c33af31fe6 c271344dab1f84f2127fbe5ff2093e79efbc98f36d0886b610dac6246208b466 ad6b29966f925ccf033156a1c6bfb5d24df40b3b37e85cedb23fc36a16398cd3 3a36b269563e9efcc10839afdb512d1e30e771e82b0c56e7afb1b45bbd0f91e1 5015b89c87924c0cdf6d903c739ab5e2b3792b75800c8030f38a890a724cf95c 86b06a54f1d06c3d45bf7d22d8c04da9813aed33fbcbe09e304c9267e9491ba9 a117fa0819fb12b6bbbe16c17dd5238ef27b46cb796a91af7d4d4d3a924bed1e

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