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-10T08:20:09.037Z
manifest sha256738f4351452016d087477e210aa4bc0caf4e7a51075ec5d908e6f05f9f953f6d
html sha256af566e402bee34d5252d2811cb3b5f4943580acf7e9bf6003ff34be0b695e13c
proof⛓ timestamped on-chain
txida9b4d8ca1d4bfa6628428aa190da6999fc5a5fb6e8b8e5b1fecaead463215bbc
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 966,116 · 8,653 confirmations
SPV proof & how to re-verify it yourself
block height966116
block merkle root91242058299aa1674acbfd5ead68ddffb7a60a2e34b3e5d7fb32b45fc54df2ca
tx index195
branch (11)b909951bc1d7a7514b341b5c5d76974d1edf72ea27aa68e71c5831b163ca600c 10fe577303bcfc09a73c2a8fbcc350ad82b98f855985fc45aba38107ac526829 6ec78361b2efa3f323cf157eea2bd8836227d88838dbb4c19304073143b1bf3e b6326ab04cb8533c50b5202ffca53f8cbf17f8143635b18e53398d1375651a5e 8b7bad135fe104a2086c0161c75a29c59f6fe45a69a8cc25f2098a5879f75657 b3f91df5b8f6d3fcd1e93a24ef8fab418d2f736a44179a797f40ebd89810981e c7f68f66fefe420ee6f9857b8793e2a9142b126ef0d81238c13399ff11a20c34 16ac0486366d820ea5e30fef51f0666eb979fac0f8ffec3057899915df1a3209 70b8edd3b6dea9e786ed3957bb217a74d879047ba86d18f920cc044f7cb5833e 95aa0c3c99579fc9a85db4706aa57af3d9e90bd5bcc41e8ad467334d04baabae 610b77f8c32c35236a5feca4d9b7712f7a40d1459feab0c03e605c2427c8ebc7

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