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-24T04:20:05.065Z
manifest sha2568e31e940cd24a9cc2e9833434c44dd553d951c7d576b0dcb6b2346e5ac5f3890
screenshot sha2567690736f43eed0a92070907fdee2935e239d53f88c9bc371df15ab38672c517d
html sha256b0ff0476379251b5679c888e42cbee84e22b433611fc81ddfef98a8a736716ce
proof⛓ timestamped on-chain
txide5f8c26dc7875852b76174ff5f8becc14208a2fdff43023ef4379b31a74b961c
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,658 · 11,111 confirmations
SPV proof & how to re-verify it yourself
block height963658
block merkle root007c6f4d41e5305815de7d29c8fe36d60cf5265d8c056364a4945ab3114817dd
tx index1582
branch (12)045a846f05fd8a22b5492a3cd8aa28727163eb2c8b22d644ec999d6c3d14926b d7b1564c2a1d300aea75d57c37c28952269e679b9a0a6bc79af088fea41c8093 836df7e909d928344632b668334bfa2fedc1552d3fd114688238e7ee3588a912 f70ba73e4c94606fb55541bdd7aca10d13e01db3380635e73392a18fa568f39a 9a08edfd6f0c60f624e02d5853f1b2d18b3a026665bc3640683f5337dca27975 0e6669596bfe1477bbdbfed10670e9b5258298753226f72a83bda32ac2386c3f 162df5b075515da622094b59ffdf84d85429c5999998e403aea5cdf1a81bd9ff d8303538689a9bd0c662f0a38f45669495c2e36e7c9d47a204eadc5451896ebb d916cf7ff02aa37f403de6ededc24e707697bc548ccfd6603b3f3f5e14e7e679 40c9ae502078f7179b467348580efa6746dfe14c75cee5578ca3c8eb31b053c7 566ee786cb0d4d1dfec34eeb4df3766788efa8803f32970e386de3f24446735b 86d4e1c3c048996245a9fda5fe80d8647e06893abf2b26e6d4d7047cd5ec2d6e

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