Web-page notarized

A tamper-evident timestamp of a page's content. Verify any proof — 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
captured2026-09-07T08:20:09.227Z
manifest sha256f857e0c6208362201069fdf9f66cc47bf53d713a75fdfe8bf3c8689d67ee1229
html sha2562bd67d7b5ff03d99392e70125d10293a2e82ff5d7e3a6477b8e4b280dc618daf
proof⛓ timestamped on-chain
txid56ca6d5e9a525374dd926c291de2b6e17448fd1f694d61604b70e7f44c785b09
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,690 · 9,079 confirmations
SPV proof & how to re-verify it yourself
block height965690
block merkle root8442fbd84d39f9d4e2df29e3deeb435dd595ceb2fbcbe69c8124e804156a2321
tx index641
branch (10)cd2472f9ca9bc1e4a8398f5bd145f006c4afa39227cbd630e66ac6c8e5fd8822 594dd2bd2e46f7a93a56bfa3a5764be2dff0be3a7f557070cf38cff87bce7d36 73953e689d7d3922a37ed7f775de8e32c4d1c3374bc06e88bb0d782d0c31894b 8bc11fae5b75478bd1894c40ecf65ddaa8db38682f3e9ac7a2f3de9abcef5535 8b6c272500b8cc4c23d927eb0eae7dea6388b216c21f9c161c35bc48a182ceae 6970f325802ad277bf23ac18b4e770a7fa31b5513eeb2d66a5ee5cc2ee15a753 5d7cdaef605edb5e70fc1e943e9e605e9b9e66991873b79fefebf4da0dc70be1 efcc633dc4b28c4739a903fd0ee1f3ed6f4417812f82608a84d94586e07ecbc0 4b368384b350e3b167b6f289228a3d46160c82216547550caca4d59cb9f257ac 0dadb6ae06fe309241d6e55c38edf3f8b31a3208bc7c95b704fed58e64709765

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

Other captures of this URL (179)

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