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-10-10T20:20:09.159Z
manifest sha2567a4d02557007c0fc5fce997f2827caf3958d6631ee12e406a21775b5b50d5ecf
html sha256f8e8f95cf2ac2f5c9ec0e87bf8f5b9dd7a408219e525cc0bf73998da2048f935
proof⛓ timestamped on-chain
txid8c109682d69dee8e0e1161d0c1b93ae6917d3164dd3691613a4d31e65ca46d81
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 970,497 · 4,272 confirmations
SPV proof & how to re-verify it yourself
block height970497
block merkle rootc9e6c4a4f72da0b18cfdf0525458b1566b2ce097a91802530f7fc7afc6490746
tx index2115
branch (12)2aa136a8aa0fc37c376ad62c15e8109b4c3d95b04518eff3a720170d8cdc5ac3 87966dd8c56c4863999471ce0f9cfbf22acfad1882dbdb24bb8e6276c4496dea 7eddc97ad943d0f4cc18340c2e43bed5d851824272f44eed837a529bf10227fb 894705c15af0664d7f20a947a1eb7ce82c3c47f34dd7a757178b8908508fc9d7 e7571732ced3cc193c413e0a032efa5a1fc5c37b79d5e73004419cfa4d0a5b36 f0a707f4e7dee213b50c42c951a60828841d85b0b9c373d22943ec814dc6b3de d769cd0afa288f4fc1efa13289ac94ee074618a49c90efdf89e2e5f113359fa1 f2f1ccf4890b89f18631ca52f59c5b0594c4a5e74cd7c59e3938e9007041ceed 88991e37139a04253258091fbad610d67e160b18e9281530079976e874983701 66b18f1f0cd0859f67e8b8f50e147908101f8334657116f1e6e2f3e482f5fa7e * 52fa17d9e17f2e5c044e1b158fbadc0a643fa2390443c7ae0df27b06624413a4

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