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-19T04:20:12.564Z
manifest sha256c22e277861ef4f1ed9d5d77ea7e0229f9cbd13662e0d1706298d6eee388ad2b8
screenshot sha256e81c33493a87b8c3ecb3e6890be9e672f70fae3b0f863da5090fee3a52e2da9e
html sha256338b2cdb098d74e5050e6d39942a41488c993864b6fde5156866cbf80d5ea46e
proof⛓ timestamped on-chain
txidbb19d2ad373ad5114876ecd4ec95b32ccd79fcff361ffe8a76a07c488a69f8ec
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,944 · 11,825 confirmations
SPV proof & how to re-verify it yourself
block height962944
block merkle rootaddb131c218daabc9e9e29d9b169aa146d70776cfd022d66d8120d0ec7b985f4
tx index593
branch (11)f95df9682e0e534d1628f13fe641a646d1ce3d4454e0e2d5900a585863cb8b33 a5b073217be5090c3cb4c6566725d06acd6e6115daee9663c1e7dcdfa4a2ad8c bd9bb53735dcb7cb3b9ac408fcb807d1c8f54c1fa11cb1b3d813b52a4d286a66 1105c8b94ce21c7748bcf93baebe1cbd32a7db0328d5174a0ae1bd4ba8565d4d c7a88f5b858c6e905d36447a8465724863770e17f57457da29953d83335443e3 09963cf5f626bafd5dc81f6707a5a597114b8026b04262622e18b98fb03c875d a476443f894f940413b19dd8acdfb7188492f8778ebffac645124fcead539381 5c26d4c4259029b9604941319d1fd95cc91d399f6806fb3d1f03a1ce711e27ef b19fdd611121f66c8b22eed446bf5e9ab4edafd6640fb32d2c848527ac545d03 d12f74df5b0f15c8281118129cc9369675c91000899cb599c601b59efcd393f2 325485f9543bbd1533ddade560c5c7aa21ca4efd3f892fe0325153b6bd348258

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