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-10T20:20:05.433Z
manifest sha2563e2b096fcbcfef66f81bec481eca744c67148e5be38b282522fd2259b75309e1
html sha256af566e402bee34d5252d2811cb3b5f4943580acf7e9bf6003ff34be0b695e13c
proof⛓ timestamped on-chain
txidfca3214c5cf282381bb88eb6dee6e0cbacb446ba17640c40545db771aaeab855
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 966,194 · 8,575 confirmations
SPV proof & how to re-verify it yourself
block height966194
block merkle roota33a64a1ca68523fd9e53c6bb5141b90a82b66fa08c07bcadb96fad7993c944c
tx index883
branch (11)a4d5371c6d9efb13c4226dd07926e11967582c0696b7796db3f5dd0f01c5917f 2dcb93d006f98dcc1b248eb03a55e8de1a57bab5ae87aebfa9cf3fecf1c3de09 f7bb51547c41d328bc3e0690d0e8b80975608719d91bd789ea38433e1b44a55d c1d02e72e5df01029e775a0c19af42d6ce796be9f5f423c11f2b6122c76b22e6 1ee6dd0497c5eb6a84bbae37357d0b5dc3d1a60e7e2e6891ccac45f218176f5d f1856aae39d6e15e854bf70f5aac53f78585952f919ab39cf3dad759d27b89ef de902fb1ef6b33bf549d01f79405c068ed9485c48a9ea2f37f7030dda6ec7eb2 70a5c414d206e57991287157c9cbf92ebf8869098f01977497a0bf6b8fb8cc6e 98d916b41be894d1add39f1a6cbabe7024361f7704f491b6b5129606b27c1c3c 2f0017223e7274594ea5c8556dd818268c82e64f6f154b67e3520f186d525e68 c8ab0dea16480d05ce2c080a7584a8a266c264e95d4413425d4f0dea79f1e70e

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