Web-page notarized

A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one

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-22T04:20:04.709Z
manifest sha256d56ca2250e166ea15c05875d3ba5477bfb4aa0ad798c52292e8bca11b8371262
screenshot sha2567690736f43eed0a92070907fdee2935e239d53f88c9bc371df15ab38672c517d
html sha256b0ff0476379251b5679c888e42cbee84e22b433611fc81ddfef98a8a736716ce
proof⛓ timestamped on-chain
txid24ed784d24f5148dec1fd147d7f37d1922a75694a3a417d2c01ac9f44e5bc9f2
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,386 · 11,383 confirmations
SPV proof & how to re-verify it yourself
block height963386
block merkle rootdb1d249ab73ac9c6722392a49a79fe8172e39a4dbf7b9862a57a9e6a5ffcc4be
tx index624
branch (11)425aa089e7ee55cceb48c8610d4b1c46725ca4513e86b8fad74d951e96dddd8e 18fa2352ef55d23589aab1c9a29393820eeb15f804875e81781fc5930e9a57b2 3f5f897e4c6d507495ce3eeb66da4530f4a84e38ad4974dca09135b4736a83d9 860477b4b041de1ec795fb9cc4aa9dfbbfa90a19ff49462b22be9054a5984e80 b41c3daee38680bfc58f1ea01aa75f524e9141b39aacecbe529c1079e2b98166 58cdd2978c998112088d24df92b175e912b1b88195565ab72ed243142496322f 6d674048123cb4ebb0685c44a540211aa1a875915fe95d156f60540f1508ceb1 7769acdeba83086d51b55f14381fe1a6cde9e206ea14b2921688956a25b78f31 060d18474884637eb0a9468305bcb7469b09e1f37dc755e30667e72290c34830 7b0b67b9c1e2977f29bbec1f3750d3e3193fb46fefe91afbfe67b508666ce5a4 06094f1f2266a4e3e8d2a839387ff1f75101a01c1fa43ee2b7307286790197c0

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

Other captures of this URL (185)

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