Provider-reported, not independently attested. Results come from a third-party public RPC endpoint and are labeled by the provider as validated. This page does not independently verify consensus or compare two providers. If the provider is unreachable, the result stays unavailable; no balance is simulated.
Latest reported validated XRPL ledger
Make one manual read-only request and inspect its reported ledger index, hash, close time and source. A validated claim does not establish freshness.
Public XRP account observation
Enter an existing public XRPL classic address to request its native-XRP balance pinned to a specific provider-reported validated ledger hash. This makes two manual read-only RPC calls per click. It is not a wallet connection. A syntactically plausible address is not a verified address; the network provider determines whether it is valid and funded.
Never enter a seed, secret, family seed, private key, or recovery phrase. The third-party RPC operator can observe your IP address and the public account you query. No account address is intentionally stored by this page.
Scope and limitations
- One manually initiated ledger query, or two read-only RPC calls for an account query (validated ledger header followed by account_info pinned to its hash). No polling or background service.
- Native XRP balance only. Issued tokens require exact currency plus issuer; MPTs have different identities. This utility reports none of those balances.
- Queries always use XRPL Mainnet and a validated ledger. The provider-reported ledger close time is shown. Live results more than 120 seconds old or more than 30 seconds ahead of the device clock are refused. An incorrect clock may cause UNAVAILABLE; independent consensus and freshness are not established. Failed, malformed, or unvalidated responses never become synthetic zero.
- The public provider may rate-limit, change policy, become unavailable, or return errors. A single provider's response is not independently authenticated consensus evidence.
- No wallet extension, signer, transaction builder, funded transaction, API key, cookie, analytics tracker, account history storage, or user account is used.
Source: public client code. XRPL public server documentation. XRPL account_info method.