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

page snapshot

captured2026-08-15T08:20:12.123Z
manifest sha25646b1b11ff9d08bca539a43f5b21557e98c57c3f4428f86537c4ba27da8986417
screenshot sha25638ac61534ea607b18397754843f14204b9c939d962a8edf0c1b7922502cd6ce2
html sha256f70d98511207f066377cf403cc805738c32820a280bfc4474ffa6c9348439697
proof⛓ timestamped on-chain
txide4cc0d7eb308e1a42bd14e4dd0d14c5a07558c633618962711ad19ed6d46b2c6
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,402 · 12,367 confirmations
SPV proof & how to re-verify it yourself
block height962402
block merkle rootd1c1dc56463e09365c03d94e53344e6182ddf79f972688e301788dc07e954f7f
tx index48
branch (8)d36f794dae3e25b1d12fd788fb4f0fc78bfe8cdac9a88cbac2fe70d0751e3f3d 99bdf285f6a1065c9d337d9500911527e2e9f5322c529396dfcac2c76180f872 1bea8e74e7220bdd851de26f2dc9c09da7332e0bc043a9c41f1389ae4783ed5f 1f2485c4867e5e1653a30cf607bcd6a9ddd71a95737831a09707957a0ea865bd df26ec2df1e0628cdf455d85bc1bb15eb349799cbf5e2ddc871d447b7f8d47c3 47e232b3632d1f6744a4a66d183285fe3c1e6e3fd24f2029a0cf8d0c80e1d4dc 0a5600449ffeaa01ed0c985853b2ee74d42b805f8559f093a47d7e7b2c88994d aefe4f46fb8934414ff2802b0a8ed4e576f519f685a417f66f9bab0ed5692c84

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 962402 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.

⬇ screenshot (PNG) · page HTML · manifest JSON

Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 46b1b11ff9d08bca539a43f5b21557e98c57c3f4428f86537c4ba27da8986417; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 46b1b11ff9d08bca539a43f5b21557e98c57c3f4428f86537c4ba27da8986417, 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