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
captured2026-09-11T16:20:05.611Z
manifest sha256e82be96e52435d69c7c82b12d533f87540772f697b3d847657d09929c3c5ffb4
html sha256af566e402bee34d5252d2811cb3b5f4943580acf7e9bf6003ff34be0b695e13c
proof⛓ timestamped on-chain
txid051dbe8c8272ebd0ad216e3b701a8e4f733366e4bc8a4a66b738bbd0f0989f67
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 966,308 · 8,461 confirmations
SPV proof & how to re-verify it yourself
block height966308
block merkle root9f26df15fecd5624928837232a8885cbf77b8a4464422b01d1def735c9b602f2
tx index532
branch (10)1088350cbfefebca9e688d5244e801a5fb7418ecefe3376f1f8e64798bcb90b2 76fcf3b93a14db71067fd4c96d7d70eb0bbb12f05f8ea0d0d7e994f004412b8c 759d958f24b4c548742d3abf729be521b6c6a542820560ab244eb845734234bb 061301004469733753e0ba42c1d7bcb98e146f1ec3aca67bb03ad75847320fcc 579ecfe9da745d7e8a2cc2d561e4c17848f93a0f3b9319550e0a1e648857a656 3677a5957526183b8048183ad5b1c8acfc07e62117e1fd3d597f75ff68af7ee4 663e3eb8eeb305acc2d158dc29d35b020b7fc2292e8ed461c560f26e3cd3c784 97024a169bf700fda835b8a35094666c1eed6918a526accecb103223a6297c7e 046875aa2304aad51d29e50f494c44534c19251ba7eae81206e8d262e656a1c0 61450ea2963a850b2ca3b786261000a8a5e5b36e660d89705cf8722869864d87

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