Soroban testnet ledger reading… ledger close 5.000000 s ± 0.000050 · measured, not assumed read-only · these pages never sign or submit

Overview · Stellar testnet

Three contracts, one shared code entry

Remaining ledgers per contract, read live from testnet when it loads. When the live read fails, the snapshot committed with this build stands in — labelled with its ledger, never presented as current.

Reading the chain…

Our contracts

Reading the chain…

Three contracts deployed from one Wasm, so all three depend on a single code entry — see the dependency graph, or what each contract is for. Their remaining TTL over time is on the decay chart.

Scan any contract

A permissionless read — no wallet, no signup. Paste any testnet contract ID for its TTL health, the entry that binds its expiry, and what extending would cost. Several contracts that share a Wasm belong on Blast Radius.

Data keys — optional, and what they change

Contract storage cannot be enumerated: a scan reads the keys it is handed. Without any, only the instance and code entries are visible, and the result says so. One base64 LedgerKey per line.