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
captured2026-09-21T08:20:13.633Z
manifest sha2561e39911f1c942422c33f5e56fb9b62c9a5bc3bca2b4e46aa18c09c8cad1b5b5b
html sha25620c2bfd6fdec83ccbbf81e9e80b1c00c73cb38183e90113167d90219f8bb23cc
proof⛓ timestamped on-chain
txid47446e836884533d817a000aac4e0851b849f2d51f339b90da4101c57811a483
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 967,700 · 7,069 confirmations
SPV proof & how to re-verify it yourself
block height967700
block merkle rootdf92859cffeb0c1938fc6d33e7b84141225f8b4c7c41c48de3e150a89bdc823e
tx index190
branch (10)6ef873958dc2c7803d9eef44cb1ac8a8c1e8f3f1b3a68fa05750af190a8eb338 7f5ead7fd47a52acdb4326fbffc675b23d82abf47839fedfbf0f7f37cabd15fa 7256a456543a76f0b20addaf12a4e7690e54cb96cd94bb7b58608ff375b2d441 3f1571f111109bacb6797ab3d43de6d34aaccbee2e17d0058a8a928cf38e93ec 23ef0e434893fc551caab21458b478740a9771f3f21189443207602ae658805f bb6dc9c1df4d243113fe2f6db5dcea23626b698b9d1d7d643631f698709eadb2 ec94039fbeed5fd2d939a746e0c01d0709253872d7048e3aed65155d487098a2 fd4bf9235e25c598aa1fd7834a5236e3156196a7d65d72f29f4a5d309884109e d7087fcb605bf54e2b8cd9bda21f6462d5fdb49e568aadc5836aefa6ed4b33d6 82e69322a409efe3bba0891c91ca04d11216bae73fd631786b8f3cb51b25d85e

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 967700 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.

⬇ page HTML · manifest JSON

Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — 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 1e39911f1c942422c33f5e56fb9b62c9a5bc3bca2b4e46aa18c09c8cad1b5b5b; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / 1e39911f1c942422c33f5e56fb9b62c9a5bc3bca2b4e46aa18c09c8cad1b5b5b, 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