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-09-05T08:20:05.160Z
manifest sha25603ef584546a90082e9e6dfe1d4654815e9bdba0b819868b943b19f9b70271a47
html sha256e80cd75230ba7d9ba7ffa8fc8937317fdd5bf455f2515b9eb458b549cc4db772
proof⛓ timestamped on-chain
txidadc67dcf529c2aa2976a91a56fcd22a339d65eee20c93d2ebd6cb72e55273a2b
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,407 · 9,362 confirmations
SPV proof & how to re-verify it yourself
block height965407
block merkle rootf001b90c7861a3c0d60a7441a1dc70078544d4698591347f0a51b17f8e2d2ec8
tx index263
branch (11)4bc1e07dd89c7f5605e4267ce509f2b0d95135e5aa8030d10c5da8e7a845ac69 727e5063acb8560dbf1ac42e8df14274c6e16c9878e9e46b9c852158002059e2 a0459090a9d3ca76e9905abcd96f2e7178f66277538c65c58bfcbc9451b0f65f a4457178baf4e1bef3dcaf842f8cfc2a5eccf1f3540dd700544af90f2a461dc8 95305da592c56d0701b7f5b742c9ed9047d00464355642fc84498b3d9ed4d8f7 c16664e4020dbb8a86be230cd6282ea6aa247db629b21fe5ce4350ce26d0d765 c45822bd91b09b3d10ee1be079eb35eb67ede15a227710387ccd2942aa37d8a6 940307e3cf7ac6bbee2c26a8cb0bfddd1f0273a445c3015d11a66195e819802f 8df1be83f5e4a0f1e30fd418bd4456a7f19d74c99f9d41c786969a03413e6c09 b60a4711539d65669ea68a5294f46d9beb28d4cd2714e395f652776f0d882fa6 d9191827a415de671d29f571d5246ef9952116bfd58ca579ff8e8bc1c018c847

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