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

page snapshot

captured2026-08-25T12:20:11.987Z
manifest sha2565115358c44e96924787a5ba48a63a1eea6b9e89bb2bedcb43f8063a3306626d6
screenshot sha2567003a69ef1de6ed5ea5a99aa30a0aaa101a0f443cf0d876212b96bb99a398277
html sha256f0db594faeef1db896573b78809ee5ae9048f3bbc5cfd340e8faf85ffc44bf08
proof⛓ timestamped on-chain
txidd59342ff7bc697a9a6dd31a9916b72d942a0473e535044300d59e0c53bad085c
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,845 · 10,924 confirmations
SPV proof & how to re-verify it yourself
block height963845
block merkle rootd254ec94fc74314f48ad91587057a55daf6088b81783417cc62f83c9bee02371
tx index472
branch (10)2423fa686beaa19a98c4aa177fe3f286358bc2faa4af0e46b05163fedaf1d485 6653f9259f37cc4bcad699381d527e6d95a58c26826cbae0069f38d3830189da 5e4c8089b48a221b6c481610898de0f5d82b9a14ee3ead88205379ce72fd2cb1 987614e4c9d0e7aabed300581d861aed08901e189219177262ef8857d44595c4 d17f4498bfe2a2b98e6f76892c5043dad969f7cf0fff98a48947aca74ca21631 7368b88336265a28505f3a7da84e5ad29219883833c2dbdc18199d726cba684f a7019c79d38c15460956d38ec8cc2f9eb8f8adb01410e2c4b07e443dbc8a54af 940e4441d281a0d83c5a2a118d95864a01b7b9d99f25ec84714c907b8f4b5397 04cdf036e7a0d35fef085bbb21ff6413676904d189e6d7863273f2541c460c22 e7b66a09d312e75054cf22c37c2cc4d7449541832368ee0b37ba06c21f486495

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