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-10-09T00:20:12.787Z
manifest sha2568cc5a899f8b738b3fc6832d316e9b2a0b5e3ba0a472b12b96ae55cd364e83262
html sha256527c8174e5a09244b9be0b238c2616547fde29e5a20c95e95316e235d2ad7623
proof⛓ timestamped on-chain
txidfb468fb2706bf2c4f068adb1686c00680b779e19208c2cb6f13abc6d35a7b31c
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 970,246 · 4,523 confirmations
SPV proof & how to re-verify it yourself
block height970246
block merkle rootd16694934df1de4a86cdf8a976efae0db98ce87059d8543d23d9fa069aeceb67
tx index432
branch (12)911bd62f6d5edc8f87c2b0bf52a726b6730b95cceec0a219d61ed34ba2710108 b9bd53358779552c7cb8475c23ed288bbf3dcf9d2042b764376af6214e9a4167 913a2c7fdf6a84dbe5aed504602451e71933ba966260aa380e703c59ba31be5f 21863a5d582a22fc76a9ce4a8121108dccc3d0c18a148a54ce89ce43fbb7f7ea a08b25dd417493d941bca378a65733fe6a75a95c8ab504e4368e1b4c3e8a59e0 025626b1dd795ac29f5e13dfec6e6f6eb496fd7f0bde9795a1d8584a41a33b43 871c50d95e3d325a13568acd147452482d4b4d8b3f8389fdeb3904c73eb19ba7 fc3c428e5d618f4f1a0ee3c085fb11141e5c0984d9fe3516f166ece843ede91b 5fe58309c6e7f2f0ceaa4c90f1cc491a67d1717673dbc3c14df837d819cce460 1beb2153cd0a5ec443d24b0f2ac2f3b36358a0e76c8cc308797a3d2fe3a033ca 7648a213d33b7df3dc1376fb62f610a658930c2b49df405879d9a1d009821f83 52420c08069235b592fbf4cb2d073ee1974006ea1f7f62d3b446a6b33df249be

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