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-21T12:20:12.247Z
manifest sha25687d7940c913f6cded4aec23d385e4778d22a2623650a749b7d3327ca663ae852
html sha256cb5f8e60095796091f76faa4c4a0101803659194f87ee0c2aca792d0550f8ae7
proof⛓ timestamped on-chain
txide88b8e4f156867f86a856039af104bc47625f0db86bc60e383d5b3a6b255ea63
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 967,724 · 7,045 confirmations
SPV proof & how to re-verify it yourself
block height967724
block merkle rootf16aa14a9b71fb11da0e8d9add1b1eb7e45edd34980908371b0aab32e473b524
tx index222
branch (12)8fcc49f454e9758522e50e08947281d19e8a1ac9bf0fe6f4ff7bd434582dd1b9 822ba7b98ad91e3e7ab90cada8816ec320aacd10ad96ab9c573bbcce1c79344e 287e075919eb671df87710810a118683494dd126aa7db030fb8bbce3e9c4ee28 394915e632a5cd29edb8572d8cc8a80c11e9074a640501c8064a6f2a1dbb0d23 4251555b3bfdb7d58e10b15a5e6697207ff632dc2a7c19ccb77d3a04e0988fee 48819abc0b02082902124ba7fdc60bf9445dac84b7a07f7ca38bf52088254f95 fa88c1be3cba4dfa0268ea8b9f2755be846d388e17049e33e6104ab3d433a215 02db48d9b19b15cd2e49c0b45e9f64751de2e3d89ddf6ba560662b2e6f660ba6 4cea48835784dad7a3e5531766b02ea0c964885af7eb8c7964aebf64b5336247 fcceb59ed49cfe216381256c1d450ba036f5c13f76a2bf6394c8d6a933a9c03a 1ee1d7a0881faae9d25030894c798a163e7b708a95c42ae8d47bf8437dd0ba0d e40d1c62e13684ebd8d9405373eb91ab3db4954c30b963ab81ab7edb68963357

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