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-10-24T08:20:16.919Z
manifest sha2561d7f3c416fd8825e4821889aa69a6a36760dc282673d613fe3258645b6ff89d1
html sha25690280d558dad396c55c8cceffc32392f15ae4885c94afd0aa16b70e7426fb526
proof⛓ timestamped on-chain
txid524caa0dff52b9bba4770eda595a01fcd4f5318e0d0bd793e4cf19c2a9901f4d
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 972,434 · 2,335 confirmations
SPV proof & how to re-verify it yourself
block height972434
block merkle root56f629861acf6945a549cafe5e3c334926fe03e3e4ac058963c52732acc75885
tx index989
branch (10)8bf4986e4d01a17773d8b6044898be41c59fa1222414c8ebb00b53693f14a7c1 94ea7cf0c1f5f4342c45a216b5cff783b334c9ed211431e7edc8e8263e4cb8b4 c1c315e91a1302467d166adafbcf8af6a6edada0fbfb22840b980babc92e9519 45a311e4362ad0ed9e626b09d354e2570aa4ba1e4dc6d9e36742eef5b9c392a9 9e3987f7c4fcf2c97a36ccababcd2a6bbd986bf26edf25fa416f8b19de75dbd9 e2ae213615ac07697abdec151b8e7638477ea89dfedaeba7b662284fd12e63ce d487863a4763da6216bc8cc3278346c2043356c4e5a79126a85e9caede45ead3 3d6243a53bcfa1ce4ecf912ce8b3f442e4bef59398dd52db91a232d4eafcd631 c1f2462e09390e7f390837c90b7a7af2726684e2d05eaea97281d426f10cb03e e62fd4bd3f66be88cb446929db7d4cc6bcd44c83d9e4abddedd3269e2c97a984

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