Web-page notarized

A tamper-evident timestamp of a page's content. Verify any proof — 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-08-27T00:20:08.126Z
manifest sha25618cc12d316e79aa3e0f3c73d329c08b337ec5c2b68c89931fbb6e227e39749b5
html sha256412a012e5b0ed687d62272453aa44fa62dd87a9782c103c8a363a9d08c60d058
proof⛓ timestamped on-chain
txidfbd98113fe08f89627e183a15dece500752cde42f38eb660db3c2b1892a3528b
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 964,064 · 10,705 confirmations
SPV proof & how to re-verify it yourself
block height964064
block merkle root166bb57f8cac267baaac3699c073597e0a189da84faf117ec1e4808927b7e3db
tx index1410
branch (11)152f943517efc0e9ea9285e5a87d4b9b1aee149417a60bdfb6567eade593acb5 0572645ed77c7d64fd54fe5cc6655cc908c1790cad75f9e134d78461151b49bb 3ec830aaa93d85d446fad4a976419a756ad3ab5c6f12a9396dd535211a53a4df 6d0800f18b6d1c75e3a3c7a3af41956ce66e6dc2c084e3204f254b50157f1f47 2b53bbbbd2668f48bb46f5c1fabfbd26efeafc7786439fcc27a1ed5236a4d27b cae4abd1899e40ee6dce94ac5a18d049a063870e524846f015be7bd7a5a8dd2a 91892ffb3d2b08c51c22dadabee1549f147b50a20b31c12ffaf03eb4c4d761e7 3d32e0a4fe883d7166be9b1082a2c803a074f3bb1b0a99f80204b4bfdea13f22 cd3ec0c1d39ee8507dcdba2fed827c2dcbb82caff37b7d88264ccbc3cd275b5c f83cc1cfedef843cd3834cd30c5129aa76d87a1a74f7c47d94da275d4c133597 82be5ad612f31cb25f58aab342c93bacd5e809f26dad13774213b270db488833

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

Other captures of this URL (179)

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