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-23T00:20:13.102Z
manifest sha256ca7d502f44ba1fd04d8161b77a5b2e6c45fc7de071f6a55f869a91f82a35d591
screenshot sha2565ac355546bdd712ab9c6a1c0fed1a1e99f5dee90069059ea7e809c76426501e0
html sha256fea4e085be35c39adde740af26b2ac9f2d3318e4673a23b9a0a1294ad9365b42
proof⛓ timestamped on-chain
txid359b0181f827c58710e8aad0d40a6c2c11529ba608507c78377bd31e006d61f3
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,483 · 11,286 confirmations
SPV proof & how to re-verify it yourself
block height963483
block merkle rooted0fc8dbb441e70b68f1d5a8ca5632b4e459bce5851c397605fa9b7dac827461
tx index502
branch (11)cb918c4ced34bb7b57ef1bece81e92839d50b099f3960365146eaeebbf9f7f22 fdb7481233b0dfc4b2d4705e791c949cc545dd58a339af5ce1b06dd30443ec3c a0c5abca80d1c26a9d16c1a4373a20aa7d73f3845bf99be5390f5f6e3daddc4d c65714fbaf1996fe568b57ec5521b98268315da04a51be3cf3bfa6e0f15625bc 716b2c6ce5a1e7bbce78e51f2a3a80c0200b953441527a74759a9818a0a61e8e f95ad00fc406add84a7c50c1510e8b1bf5bcaa32770e1197696eb00c84d8dec4 13017c5a84c60adaf17a86f537fb38e518e836878c5b9aed553c41793f4221a3 1afa7387f9d9c4d7f525900dbe3664583bb85046d857e246ef0c4e08f1cb1f0a 153558b28ec27938f57385506f94120b0584191c70758aace8a4853f96302ec1 1abb8c6f01d4e3ff17749cc725ab77392611a2d4e0a986639b38a40766c0cdbe 7256d8a6679721892ad9d7764d6e8bdf68dac597fe8fdcf41ec07f7ecf781a87

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