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
captured2026-09-06T16:20:08.213Z
manifest sha25677da3441c42a94ef1de37921c4e9da0d9a709d5740caa9901546ffb3c8bff809
html sha2562bd67d7b5ff03d99392e70125d10293a2e82ff5d7e3a6477b8e4b280dc618daf
proof⛓ timestamped on-chain
txid66327ba28d5202eeeb1dce83627a5b17752038cb73e9a8243bcd2e3d7eb26dd6
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,596 · 9,173 confirmations
SPV proof & how to re-verify it yourself
block height965596
block merkle rootb72b6eeab5f54d216ad3484214520550e998e638a28c3e6b05690879d00a9baa
tx index756
branch (10)3c1d877e10255a8fe7523ef8d7a47e00ce3b087e1aaae5d708bb8228c0a09eab 4465331f0833a6d0b97e15fd2121c70553820bd3f15042a0db86edde94c6a047 e5f7181bde6caaf0c0ca369107c98897df5674facc59b4ce0da517dadaf5c1ce 65d873904efef71e064eaa6b97d5c1185d3497b3f39444ca10189298d279b1f6 8500302b775395787f71912f6154ee3003a48edc1d88232d1ac06134dadbb668 0190412e17cb10e3aaabe8f9c1fcfc9e3236cede07057d2678011ae9a6aea663 6cad454b2dc8368f22afd977d833f2f2f433025f497943ca44e1ddb712052c68 9e581de638a7c1b8a2a9631bb9b836e9b8b49bc5dabb4db0ace9d09a7b209b1a 3c4290b556d60fb0678e6456cd55f1bda2aadfc1d08525619af6a9a8ed22f170 a03a5883f6dc885caa64f6a0bed2ac1c2f9063f66c1ba546b315bbced88152f8

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 965596 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 77da3441c42a94ef1de37921c4e9da0d9a709d5740caa9901546ffb3c8bff809; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / 77da3441c42a94ef1de37921c4e9da0d9a709d5740caa9901546ffb3c8bff809, 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