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-13T08:20:07.854Z
manifest sha2561137109a7806364717b2c009adcf74c21bfa778357aadb8ee7808f3c19a18fe6
screenshot sha256c29485f7365a623af98fd5e18bb3cb0aceb40c5b221940630561fd6a4fe7a883
html sha256f4dbd95b780356fac5ac537da92dcf23008b3063295afe6d2e37bfe9dc181200
proof⛓ timestamped on-chain
txiddc84ade2f857eff223abb29b5a2f8000de9012baaf99439ec3d871509fa70f5f
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,107 · 12,662 confirmations
SPV proof & how to re-verify it yourself
block height962107
block merkle root4eacea20da640571c75fa683be10af92bfe88e13cffd895aa43d634018628a4e
tx index114
branch (9)e4ab2e7325ec84f784e73ecc034402bd410e4a3711085943d1f27287c1ad5c09 dee103c313c31faa4cdc18c06740854ed91df54ff3d468ad032bf2fd93c63eb6 810a286c74ec2733a65d3194c30d0b72e58121ceaae66bdc7fd89693a75bf302 a577130195ffaa4e97049ebf7cf15a4e276dc1a0729a14490efb6381b6bd7789 9d304670b70035402ec7cf49c8c40e821bb5f3dad75fe475e1b719192017db32 c309eecd7b330c75587d331ee31e71daf37799073f89d177bf7dbccf07cf739a acfc92e9655b92380a86017fc4cdbc507b2a902c9db53142a70721f7cbdffdd3 e1eaf51585c8b229009c7b299d552aa1eae7515298c7bb2a2eb574c9c56c67dd 11d0cf6f3a811a983ee6fc191491d3be56a37fae22e350ac0fc5cb98451248c1

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 962107 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 1137109a7806364717b2c009adcf74c21bfa778357aadb8ee7808f3c19a18fe6; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 1137109a7806364717b2c009adcf74c21bfa778357aadb8ee7808f3c19a18fe6, 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