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-04T20:20:05.115Z
manifest sha256e3cd7cb749c154c7ade1af7d7df712eeff0399fed0a7a2d479f73c4182127792
html sha256e80cd75230ba7d9ba7ffa8fc8937317fdd5bf455f2515b9eb458b549cc4db772
proof⛓ timestamped on-chain
txidb996c5c02d8193c24b6fa6a32fd4f06868a716b11d07be9f7f9d146e24b1f4df
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,325 · 9,444 confirmations
SPV proof & how to re-verify it yourself
block height965325
block merkle root91ca5f237e999fb66b2ae1f0cfaf041e4c8bbbb0e7fa514b7bb6815c4723443e
tx index819
branch (11)f9d5b72889d7e9e860a485000987b4bbc81ea7b980a9b7e3fdaca591697b1e48 2d919ff471b977994a12e58a810b8bdb73c36ecac8f60f5b5eed1606f917769e 0158df0d136ba0d6406335532010a02e5b530f17eaa2c3bf120184c4aba1805a 3b9bbd2ad60756a8c45d29dba8e992b32a3219368dd7e1d8d28675a686121865 1042a3cd00ccbbe0e74c1b5c19f2cc1ba88a7ee3c45f4ab13c0210f61959e962 95d3cd4d207ca2de8c3d031b58e381d88cd2d21de7af522d189143d2b4a3b66e 9440a99096a01ca1a339ecd16f31cecd348419b55496f924e60a5006fb45fa6e 2eeafd4cb23dfbb1bd3a808a3c4147ed3d12578f0d472fcf725aa6e12b56b5ba 9589e2fc9ebcdd4bf38f49c2d8dc57d0e084c712f71e05f3f46e5c74bf0f97c8 c11970cd81e9a5a6b5056df0d15dd7bb975c14f9ab9559a18429e5ba8d0e79e1 f8caca288cc63bacd6346b320d7899281bbe5d92d4c9c5276f6af8f7ea8866b4

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