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-09T20:20:09.468Z
manifest sha256624e9cc65d73cb93b50c6032b3b62df8d5a818114f4cf99a8b3c38165ae80761
html sha256c4578212f432b9c4eb9c8a987986027e141677993071211e0f9a874240ac5118
proof⛓ timestamped on-chain
txid6713e953b21fb9031d586e99356796c4b657b0ca21e2c64c4cdca97f22fe2b96
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 966,059 · 8,710 confirmations
SPV proof & how to re-verify it yourself
block height966059
block merkle roote72ca51f2dd1be3b9861c016af4086cbd2108faa55434a1c93a19d2ecfa6ece5
tx index362
branch (9)aaeb402188bd7386b5076ac0de779e1fcf999dccc28d03bbfcfca217b872ec7b 58318bc670cd4287f2d364bc03dfaf9baf2fc763716ed1f9d5780688a3e82342 df94458ffd039ec421813193d2c19074e4fa891c539be3a1ad3de12b04e061ce 843369cef635228145f8f2dcc9eae937d1431e83514d174d6b3f20a4593f803d 9d8c2b777f6375691e7f107df9d574c1fc2662ec853b34ea3995d1f5c1c497f1 0c06f05a6e1b8160df90d649b308a7a3bee754dfcb2e2b6e01d0d8a9b1f962f8 f822b5948c6b1eada91b35611e0ff24b8a78f445ad76b8f00807858bb2403410 eadf6442152203f9cfcc38cff2b484a34619ffe86278656b27287e68ae8e9eae e551d12a9808eb8a1de8128c37e887144021ef9557f2e458188f952537687b91

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