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-28T08:20:12.248Z
manifest sha2562d1a5ba87169f0ef2b5f7ef76b7d355d9f6953face9375be25b4360b322f4066
html sha256a040fe063f62804e6d0a7a813039a270e7a84d17fa5422d88fd03a832b572de0
proof⛓ timestamped on-chain
txid48bde0e5d3a5a910edcd6e93a506aff9000865bbd60606923f939f344ac7fcc4
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 973,001 · 1,768 confirmations
SPV proof & how to re-verify it yourself
block height973001
block merkle rootfdf095d0b9471b12f57d515d8e97abdc552afa74b680ab0bb13e448f1688c4d1
tx index176
branch (10)74829a21ac4956d7291eac3f0caf9e5a0a109f744b11296e3c5be39753f0c43e ec6f0ee853dcb81b055622f087c6ea44b7223dfcd0695e6e0e2d8d6090b7855a 85aa2d3c2a564111532468a6e7e8762258b93544062045d7f4bb52437c6ad544 dd13c50be079bec1b8e383a614b0eabde4e74d40a90c55e00cd999d8d1a28ce7 b4d08b71a7dd1f0e18f26429f66ae0464f4706e03a91abc23cc034f0e3ce716a 56edc547c373785d9ecd496b296746f346b48c0e34f9ba91008c61ca7e7d0ce0 f84b6ce7e45b1127141934e33e47ea755f267770db064c2dd2a67ff87015fa33 c0e382b3c81dfbc8d774c8e8e178352b1fd3881e7e38bb846b9490d31812dfe5 0786b6940c32dcea657caddc923eb1c2e2bc10579318e1bf69e6162b8324bf66 16c1e096e899d0fed0dbc1913dfe48cdb2b9f424ff2459e92d64ba936bfaa978

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