OPERATIONAL serving on mainnet · read-only no issues in 8h 10m report a problem

🔎 Explorer

Browse transactions, addresses, and blocks. Every page is content-negotiated — browsers get HTML, API clients get JSON from the same URL — and bsv.cx anchors are cross-linked back to their shortener, notary, and batch proofs.

Endpoints

GET /tx/:txidtransaction (OP_RETURN decoded)

GET /a/:addressbalance + UTXOs

GET /b/:heightblock

GET /search?q=64-hex → tx, digits → block, else → address

curl -s https://bsv.cx/tx/<txid>        # JSON
open  https://bsv.cx/tx/<txid>        # HTML

Chain reads are served via WhatsOnChain today; balance/UTXO reads use a provider-fallback layer (WhatsOnChain → Bitails). Normalizing tx/block reads across providers is a tracked follow-up.

← back to bsv.cx