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-12T08:20:11.971Z
manifest sha256bebbe56e855542d032443acebc66c0b76c35f85d5e53f74a0287621a3abd7d06
screenshot sha25624bed38ce65257a6cd1eb25aefd7238261edd7da7816926b6b526d7e11dc5d32
html sha256acb78e094f36ec54aba67f4a75d2560a582ec506b088475248ea8c8ad01bbff9
proof⛓ timestamped on-chain
txidd2878db5419e2ec8d14321099188067a80150646a3d9e4537f8401f12236d46f
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 961,974 · 12,795 confirmations
SPV proof & how to re-verify it yourself
block height961974
block merkle rootee7b0739f4066b818f103ae920786a2ba5da9129d7a7b4956290344e2738053b
tx index2
branch (9)df7a150c4232bd2f4a072ae099c435baa0b62a82a31e6f61be515957ddd37cf7 d7e60ffdfb748607823b45559d7d72199830ca539c43fec2a06bdb9d582741ee d547500b67a9701a27c5ba9bfe1636b42f6d5649699db7890b90d5c836a74595 a01871c4c6213f8eda251718bdb729fb129caffdbbda6b6eecb235cf9b6360b5 23bad8cdbb3378a52965403c2ef28dc8f156992b63d6410f253c8d6249cfe624 8a3d2a2846f0a20267fc699715d0f43a27979759d9711c727f331c296e5013bb 6837ae265b5a8fe2ae3cd2692b4c0f72898672beee64f21ce2484c57ff43f032 20c99d436b4d70c1e35e0a885db958602a527b263443953fe04d562df8251548 cc4003bd27844593112c770bd32fdaf51b2c7db40c0bf1c63b11c13ef7acb58f

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