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-22T16:20:12.981Z
manifest sha2566b8cbab6c47333754875335663f8c3c983c7cb603c2244b1d394fd44dff9d866
screenshot sha256db997ec2469c9c2ff85ada96fb1a31cf66d6a7cba683aef9495bdbdeb8ba56ff
html sha2566132f0ca62089d09e60a693d8e83889fc5095c65797ea10e9c411094d3f367fe
proof⛓ timestamped on-chain
txid989db6b32ac0fc637138a462df22b2526691909a2e92dd7e7254a2966a650c1c
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,432 · 11,337 confirmations
SPV proof & how to re-verify it yourself
block height963432
block merkle root20040ad3c44f02b86432e4644dd031200ddd9c38eb24a2d239b34ed921808c4e
tx index620
branch (11)fd641c378992aa375fa8f79beab1148cf07a52b795fef415e6edaf782d45d5b3 e2aeabcdac34e14f838a6dae296bd04509b4854c0a7ca0b8ad0bd7f1a95cb998 8c870a6b0c96e69a307e211cf76ff58cda7a24615d9e71c5df59259579dc3849 5203d30c6cfa6996bcf660e057c1c530e3d0d801222e07563dbcfeec466ca97c f347bc1a5ac55d7d8614f009add5c50774ad58e520d93132c1202207e79dcf54 a36211d377e1d1cde1852e7e5601d3d04a1fa9914ee3e4453f456304e1ee9e5a 7f97436b034c8c06de19e70ddf86b96ae1c227946c477142874ab832ce737780 533f371ba03707010915a72ca3fdd89a9e572bf303679db42d37abd3fa10882f 1e96319bd47df0565df1e733b1f0314837928d939e7a86df5d2fb2b0519d41f4 4fce6117afe3d1aeee4d36aa2b940c7ebf2f8ce79b0c034f982f0ceba5080de5 9be09de385bf53176ab3689b53ad58d6c71e0a6f949f16a840322e7ef689af12

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