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

page snapshot

captured2026-08-12T00:20:08.535Z
manifest sha25642a8d3c3711713bc4821ceb95aee0e869961a900eae9f7fb1f46065893ff2126
screenshot sha256d603491fad931fd7fa06012b7f88c8d6fafeb528f108e0c367f0523cc45e898b
html sha256d32aa7543a8a50a3c2c8dbd4c9ef14c5b8fcd216b5711a8e43d5c17a79caf25e
proof⛓ timestamped on-chain
txid930b0a1ff5cfd24b7093f3230c9a27400c3c85c1e49ea6b0b96c9bca6c72e547
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 961,915 · 12,854 confirmations
SPV proof & how to re-verify it yourself
block height961915
block merkle rootdf8f92c441c51560e19d96368d7d3d44ffab2ef07f4a7554a216e3f10a80590c
tx index315
branch (9)bf585704aa6911685d29de86dbb6d34665def3f8f28dd5339c625b56f496ed30 db26dfe1976efa81aa8766fb65ba69de3c4fc4a295512502adbe1c9657126155 4dc8c5bd339c060010453b0987e317bf5758e5532426049d52017c9fef64d2a2 6a929004ee12de633cbbcec9afcb4ffb006c73f01ee861266003fa811a106b6b a239054067b02fc9626b8e2a874ba115d75e68e6bbe901368ac703ccfcad583f 3daa39aaf06023e73c339cfd8f11495e6209e3551061e8f3e2e1a3451ffce252 3f7d285baf984531e4162c5ee84cf1eaf68b895def66d8f366173fce77d08d70 bd2858d256a3386eb9ff685f171310024e74e1ed697572745b7ea45104275fe7 9176fb14b7b31e40915f81dc391eb4e55d09be51938a86e77c5f52f86b281fc2

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 961915 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 42a8d3c3711713bc4821ceb95aee0e869961a900eae9f7fb1f46065893ff2126; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 42a8d3c3711713bc4821ceb95aee0e869961a900eae9f7fb1f46065893ff2126, 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