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-23T12:20:17.951Z
manifest sha2569d947a5597a92df9e612603aee82cd3258bb766af9423a75f11b42623d4c7c0f
screenshot sha256431fe4188aea08adbdffa92d422f7f28d2ea7b8a49f99f41a3a1b2df8f8c762a
html sha256c8d21b7701e43df942e5c76304d4668f19f252a48fd73774a3b79b78248c46fd
proof⛓ timestamped on-chain
txid0e6f18bbd07ba0de317bb7b204649513f5e2f70071a6a00aec6e4589441b5fc2
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,562 · 11,207 confirmations
SPV proof & how to re-verify it yourself
block height963562
block merkle rootc15b706eb442906a629e40395b831d9956b874bc2fd41b2f79ee4a4c06f99874
tx index242
branch (9)9c4a6e2692fba0613c08429d80b776ac78c7d394bc24fa35ad44e23e40cb98df 8a66593ee24a2a35c07b3f32230ad7d0c12d51eeb6853e6f8d4a0fce95e1f1d5 7100cbdacc384bbf13ffc2219c397ff19c3d7c74e57a7868cd7a886fd58e51ab 714f3a4e81019a3094f52e289b7797db0d3d6060b39a5cceb8a2f8d20406575a a221334eaabdabb17e97a807b82e06844bab48bb58d9ce50791eed6c9406568b 51a1b3c72e74906c33bc3946287d4f292ade18abee9d97de9079a408adbfd426 2bf4325499ad5a66d367acc331cf07b13ab301b7e39f711db57e886569c3466b 2311eb68ba4d84f1ec9104a9f60295ce6e86ef860cd85b156cdc6201f8e9e816 f1f57766304cd63d38be6187a9b7a1b134106488cceac2c3ecd780550d7b1c84

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