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-14T08:20:12.271Z
manifest sha256beb70a77d1b4a8c64b7bd6e130cc599dcd0e024a046e05f3ec95df002658d992
screenshot sha25633f6b1dd5d5b6c6e90f503c1276b5766858591a67ba81e0fc2bd97b7c02b0d9e
html sha25603e94f481d40c7fdab519f42af982b77e3923f5c50e9d25a83d3f7f73ec837ca
proof⛓ timestamped on-chain
txide7c265141fd969e394c826f517d66e277104a31fe09eea55765774a3c1496dcb
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,257 · 12,512 confirmations
SPV proof & how to re-verify it yourself
block height962257
block merkle root92c69a03a0c572f4d81a22ed180eaa66d2d5379970e774fca78d3908c58790fd
tx index9
branch (7)4b2db34e7b20a06c2d7d454597970259fa9873b66df59097e0d5902ced072a5a 2170fc017b7f1e45f295a37189a4f829164565ac7598deb634f8e89e89840119 2126d80f9a32f08d8cdfd53c2e1db5a1255ed22003c4b4e3d5a7803b8b8eda62 4dbc897dca7697f3b0399f8a2a24602421a56bfffdbeb615126c367c3b6eeb10 77a3cdd2581a4a9e6508cb2afb34a23aa1b08cfdf84cd7d93df04efa62f71b7a 0c4c2428c9e980ea0ea17eb7f5a3413528d5ef01eb99f75a469a3d70b6b04f0f 432c15c629a1deeea3d4bca1646a2368baa4b72af5d363ba7a0012cdaf0ebd30

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