Web-page notarized

A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one

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-17T00:20:05.075Z
manifest sha256b5406b5154a39ac366b099221823b2b2d24ec45ffd0a7e96555cc51d6f414d4d
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha25660b93a46ff591f6966a1e326d68a9f962af61beb2e7775674458339d5492034a
proof⛓ timestamped on-chain
txid9ee3fc73eb6d7f53bc5b44b7617733e3b4dab100de85bbd6beef24ba557d0478
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,651 · 12,118 confirmations
SPV proof & how to re-verify it yourself
block height962651
block merkle root4dea6783831d6a14104c09878fef67746645f600253ff5e2a1191c76319c3a24
tx index531
branch (11)6705debe44851d5629d26bb7a5b359ad48ec208d1b56f221904958738c3b0cbf 26ccc04195c62e44700fcd73a5d86937248018147f919af9819251eaaef57812 58c2d57ff53de56a404ec19b453cb701a1a12c68eba2e1efea00cb9807c00e58 641b3bce874ab1c5fb1d03061cab7a0a70b916d520e23d7cbce017fb8d368a00 23657dca179d0767b2189672a33279a64d00414f2d411f3b4e7e82067a4002c5 d9c84512ee276237f5087603eb3ffaa6d7f5a2cfe6944ca6b8d2a4f87954aa60 d3b80bfa7cd10637d11b237a2797d5bd169ae349f68246a29209d49806808bba a615c1b34037b7a1273d75a827c0b1ab5dae8595e055ef768940e88a198e068b b2be36aac4c58bb56e79dcb2035c1c220540831b9faef912af6d9f0914f36315 c15767867483ab3903c678848896fa812c50577b9a70f4e5fb455ae76df28ede 3713d9ab3a032756ed38692ddf13c0d902d6cfacfe8d7a522768506020bcfa81

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 962651 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 b5406b5154a39ac366b099221823b2b2d24ec45ffd0a7e96555cc51d6f414d4d; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / b5406b5154a39ac366b099221823b2b2d24ec45ffd0a7e96555cc51d6f414d4d, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (185)

← back to bsv.cx · JSON · saved HTML · ⚠ Report