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

page snapshot

captured2026-08-21T16:20:05.095Z
manifest sha25645e41f75478bf75fe3dcb04040da211bb9523aa6024bad4fd3c4dc81f40341c9
screenshot sha2567690736f43eed0a92070907fdee2935e239d53f88c9bc371df15ab38672c517d
html sha256b0ff0476379251b5679c888e42cbee84e22b433611fc81ddfef98a8a736716ce
proof⛓ timestamped on-chain
txid197e0b5d09c1912ce9d9e90a281717554ed55e24e3682965bee1f62f991adbf6
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,334 · 11,435 confirmations
SPV proof & how to re-verify it yourself
block height963334
block merkle roota719ac1408abbe2908e04c85b3105ce95f0298e0529193c422e9f282e7b843f7
tx index64
branch (9)b21d7132486b56e6f7ef9472e4b5ae21f6a464d70029050ea4e24064eac33ad8 5ea9f54a18863c26dc019e07d3f445faf64420487f9ef34a36f14997e43e4893 8e99027708ccee54730cfbfb4af72ea9737378a00185c00dbee3f939ad86bf5a b2f0555ec14773df2c3945247457cc4a3778705878a09ebe86159565b04331be 3edb1613b1587fc3467560d85c8bd4d102dde24a7588f95783801f57759fdcfc 889e2732bb2dd4be83adc00a51f9d8b5f62548e39de45400cad13328a69c815c 27b0f5318929d656f73ea54bd54269fe04999467ff89bacf114ba7d4ca094143 c8acbc54f595bce2940113cc5259c68c3c2eae734dfe775be564ec6b2b16d53d df950472174f420dbeae3b586f7a9eba7ea873f83a7801bc5911c1d146499265

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

⬇ screenshot (PNG) · page HTML · manifest JSON

Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 45e41f75478bf75fe3dcb04040da211bb9523aa6024bad4fd3c4dc81f40341c9; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 45e41f75478bf75fe3dcb04040da211bb9523aa6024bad4fd3c4dc81f40341c9, 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