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-08-28T04:20:04.794Z
manifest sha256a62fbf35a9705af5fdc1a0db1ca18f7db630f48de0b9826f89e091ad05f36fca
html sha2564be7bdc1c37c48b269b90ed0722b4c4db4a8b8db68e4edc2a3c15103258ba46f
proof⛓ timestamped on-chain
txidc07087780a589517a2da68f6ee2e527928e121279842f1bef71544c9303c1b4e
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 964,230 · 10,539 confirmations
SPV proof & how to re-verify it yourself
block height964230
block merkle root3fe39b31f9842b9a524905e20b9f0552cea5b0de2ce5e66abd333595567f0b70
tx index900
branch (10)fa6bd66e46dda7c229a54129eaa529f0e8bb97da611e0de12a930c854b1f4112 a6bb2277b84e2906727a018363a15401b5f0962cec84fb0b0b2ffcc45a9baad3 a20e3752a4df7f97085d693cbc181ef68c24c7e52d9d28ced9c70d06928b5c7f db1c7ecceb8e5f6b15df49cb73186244d7c9364dfe85e2665c89e2eed199511b 0f7b457087e98ac7d7cabe4934db66cc20424b60564a3d0f16ccc81f029f2c6c 532ec9d025c2645949479f2438153eac9e50e7173b8b57d2f3e0f36d14b8f5bf ad69fdbcdf89e538b8c4fc095116480cf9ef9ae8b81e7cdb9edeae95f5118828 f040b7b7866a449689f53729da34d670000a3002c05c4f36179dce3ec6ea5711 c78d535d26d859958439f2b5b6264867114f5a5466661c1b2e427862466feacb b5b39769e583ad72019010ccffa16b9b9cb2ebb883d39ca4df925caff720995e

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