Web-page notarized

A tamper-evident timestamp of a page's content. Ukraine blames Russia after air alert app sends out false warnings | Russia-Ukraine war News | Al Jazeera

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-11-02T02:15:12.959Z
manifest sha25669b164a66b159c549eb12ae9235d414f31b09e6b827d91820d700a37ebbf8218
html sha256e78e7955be2e4a3a485e19fe1d59542346278a9b3aaa405222184ae8b5abff05
proof⛓ timestamped on-chain
txidb2fcb421d58ac1284d5b9ebc2283f8fd37ce7786c8cb3a5c4795d39eab4b5bca
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 973,691 · 1,078 confirmations
SPV proof & how to re-verify it yourself
block height973691
block merkle rootd44ec3cc7948446b1751d8f011fd0eda69ca296fb1fbb39e3a194600f13dce84
tx index452
branch (10)687a46e638fe5a7ba86bc78431cf01662e3e11194ce076fe865c013fbc37f0d2 43f6fe17964fdfd1d096270e759d2ca1bd9ff3491b6874e997565595734ee27d 3464c0e580468d2ce1325320229818cb58ef70f9d5e8469b011d37d296d5187a b9f428f7134b7ceadb3be2fece743cbca9275790df7bd67a67c94bee83c63079 943913e6f5ab462d816388cea7fbc16bf7b40289975ecf245da7861851ec6fa0 1fd50a3eede8a147df8d0a569e0a008cf824de776877a5cc62775d3d843a6493 681981b23e196d85952fabce27ac334f6021d5a959dfc2cba6f325e3f6141625 f8d4f7248d2e7fa48b9a224c648ae8aa7140aeda774e08929ef7abe1c25a8eff 5ce6b7965949ee8602e292f856c049d0d9527d41482ea3bbd190c68888442ef1 73f505a0d0c157be71e2805566d6084cec44c658e02234d2623bfe2f24254251

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 973691 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 69b164a66b159c549eb12ae9235d414f31b09e6b827d91820d700a37ebbf8218; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / 69b164a66b159c549eb12ae9235d414f31b09e6b827d91820d700a37ebbf8218, and the block's timestamp proves the page looked this way at or before that time.

← back to bsv.cx · JSON · saved HTML · ⚠ Report