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-03T04:20:11.807Z
manifest sha256ede07800e36fc48b49d72c7071313dfc6534be9fa2fd68fd5adb204ec78ccdfa
html sha256bdcfb4c0a71080716ba2d661df0353fad1f2516fc87617463e5679a203159c23
proof⛓ timestamped on-chain
txid521a1d6a0317390403d06276c17e9c9c199632b354d92d9323cd3cf306791bb1
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 969,411 · 5,358 confirmations
SPV proof & how to re-verify it yourself
block height969411
block merkle root75588d06ca6302d1447e448072fc453b10c673e039f80d9defafdfbb7a9b9803
tx index477
branch (10)3f1c7e13c0c4e72c14c8357caa70770a8cc13a46b8068770c0022c5fdcaf5baf 4dceab673d9c27bef439807ad4cf22ce271f24c73fa4da3b2dda1028df027f17 d343ee69d89d94ff879f97e4becffc797a7d25fdf2fced2f32d5a18edc94c0e6 592771c1b9ed97d0db20c7e3314ef3e70f0e1a3aca98368c78942e1dd0c8a7f4 4ee5e10862f6aa2dce13b862a06addceef682ea6c2e6670801725555fa92a491 1a6c716b8883fdebd1a5afcff4024017afa79b5031f15320fa766d33e37f6973 3e2099bb4d360823c0a00f0747d885a2770494eab741a9929dac164a51899a9c bddca29f1f359508423377940eb5f11a0d6cea8e50afa76c1189d4767a5f9133 b9cb5419db8e5e8fa41878035a3701f16c0cc570aac37591bbc34f0c2de24a53 77d51fedbc2c716e7e8909f93092715e40a774a1f78f458a349e885410846a1b

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