Soroban testnet ledger reading… ledger close 5.000000 s ± 0.000050 · measured, not assumed

Contract scanner · Stellar testnet

Scan one contract

A permissionless read: TTL health, which entry expires first, and what extending costs — priced by simulating against the network. A single-contract scan cannot settle whether the code entry is shared; that reads undetermined, with a link into Blast Radius.

Checking several contracts that share a Wasm? Use 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 — the same values the CLI takes in --keys-file.

Reading the result

The verdict names the entry that expires first — that entry sets the contract’s real deadline, and it is rarely the instance. A clean scan means everything asked-for is healthy, never that the contract is fully healthy: coverage travels with the verdict. Exit codes and flags are on the CLI reference.