Web-page notarized

A tamper-evident timestamp of a page's content. Pay-per-call — bsv.cx

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-14T04:20:11.580Z
manifest sha256d9609d23957718618be191e7bf18add3306be732049a6a48d14e3532c2a1f620
html sha256305ba2ab93c10c26ce054ce7557012b2111c6859a25eb4fe61ed17e76689fe7b
proof⛓ timestamped on-chain
txid011577536813b846b89ae324e90bd7c9e963750a11e4c56e73a3918299cb6e0a
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 966,676 · 8,093 confirmations
SPV proof & how to re-verify it yourself
block height966676
block merkle root5cdfe81f1cfd5c63373e9218c4c8aaab9a2b8f25959568debe2970c9e695097b
tx index264
branch (10)f56107a9fe01a3c4673453cb45455befcd26327f1131d8bf05a588baeaabe2c0 7dc61b17cf155ece23c27d01a57ff7c42fadf7621142641c82e7a76204f9fb23 d78c8625db84cf8c33692f2e75ed3f2907ed525c704813fe910012b3cd262573 873429c85daf13f2e9b73e04da2dcc9fbd4aac92c869e57d5f1e4fb5e376ab7d 755af040d51c7474a8159be1454b4657d2a8ad72ee3b34d7b3c7395cfc19e5a5 6891e560a327ce428382afcaef67f42b386dc5ab245466b8c1f99a84f77c78a2 ed06075f9b8d7e7ce5506178dfbe56bbf8d9de10a275983497d3147452fb52fc ed7c91f8102b59888ecf0b3056ba1e9b352fcf87dd3f339f89425aa191759a41 a4f7ae190b5320a11ef0b8b11c0976265e39e931a5e1eefda1a2c87c03ebbe38 70d5dd41eb96a497d683c8fe44ea3014e731ca9942e9cbbe7e5ad7f027122e0e

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 966676 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 d9609d23957718618be191e7bf18add3306be732049a6a48d14e3532c2a1f620; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / d9609d23957718618be191e7bf18add3306be732049a6a48d14e3532c2a1f620, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (600)

← back to bsv.cx · JSON · saved HTML · ⚠ Report