Web-page notarized

A tamper-evident timestamp of a page's content. Pay-per-call — 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-26T00:20:12.261Z
manifest sha25611050cbe18f5e3f474a680be2b55fbfdc2cf11210d4c49746373d8502edf48aa
screenshot sha256a6f337c72daf5ac60cb2fb3287da56ef71b8b6bd5c7142e94e4b512089b498f3
html sha256afaffdcd676c666c7fa5f25e72e8559fcd90bfb57c16aefd8f174b01df189788
proof⛓ timestamped on-chain
txidb3062e325dce936daa9389cb614e5dd922d1b514e1b5ad411ba40c5c9d2cf835
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,916 · 10,853 confirmations
SPV proof & how to re-verify it yourself
block height963916
block merkle rootc878410ca22a0314ca35768f6b48cd6f5d254e37670f69633d6b268932ad6f87
tx index1794
branch (12)097105e7c91d1e20c233ea689391075838c18025070d6825e6577c1f32de37f0 b77f009457d98d2e60eacb831f5b88d61563fdb4e97a11ecf515a7fa405113ab c9b770b6e2ba8dd4106fa980a3e1ebc4ae394a2853390b59feb2c915ae0a1e4e c77b08f978d2beb317050c3752af6a916c5915d24017ec80dd8f2b27073b1dc2 da04a15c8ef864ec8fd0b51f2ba72557f2cb71ec017cbbf75e2118006f37a28e d3c7f648ae8a37225b9776cab95f7b78b922afc8de7e8c4a1721fe6868f1ab2a 40106a7f0f9aa7c3f98724a91b7aae63bbb10d29f67a1afd5373592b340f47d9 d24a11a29f64d794a27c9ae4daf6d336852d97c0924180fcc03b494560b4d6d0 a2068a7fe4bc58847d6090a3730d9df7924f36b2d8f552f1f90e1394f1142b24 0889424b8f476147169989caedafcfdd8031f5d04626a6fc0d002e8f2af58a4c 7997edf372f400df29688b3342b43965948570be6716c4ce83e0a34183641b32 abc2daad23e261f6b6fa92ad01265589a4eed477180ffd737f461c02a0ba56ec

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

Other captures of this URL (600)

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