Verify XRP Ledger Transactions & Supply On-Chain
This guide shows you how to independently verify XRP Ledger (XRPL) transactions and the total XRP supply using public, on-chain data. You’ll learn to check a payment, confirm an account balance, and audit the circulating supply—all without trusting a third-party explorer or website. No special software is required; you only need a web browser and the transaction hash or account address you want to verify.
What You’ll Need
- The transaction hash (a 64-character hexadecimal string) or the account address (starting with
r) you want to verify. - A web browser with internet access.
- Optional: basic familiarity with JSON, as the XRPL API returns data in that format.
Step-by-Step
- Open the XRP Ledger Explorer. Go to livenet.xrpl.org (the official XRP Ledger explorer). This tool queries the ledger directly and shows live data.
- Search for a transaction. In the search bar at the top, paste the transaction hash and press Enter. The explorer will display the transaction details, including status (validated, pending, or failed), the sending and receiving addresses, the amount of XRP transferred, and the fee paid.
- Verify the transaction status. Look for the “Validated” field. A transaction is only final when it shows “Validated” with a ledger index and a timestamp. If it says “Pending” or “Failed,” it is not yet confirmed on the ledger.
- Check the transaction details. Confirm that the amount, sender, and receiver match what you expect. The “Amount” field shows XRP in drops (1 XRP = 1,000,000 drops). The “Fee” field is the network fee paid by the sender.
- Verify an account balance. To check the XRP balance of a specific address, search for that address in the explorer. The account page shows the current XRP balance, the number of transactions, and the account’s “Sequence” number.
- Use the public API for raw data. For a more technical verification, open your browser to
https://s1.ripple.com:51234/(a public XRPL API node). You can send a JSON-RPC request to query transaction or account info directly. For example, to get a transaction, use thetxmethod with the hash. - Query the total XRP supply. The total XRP supply is not a single number stored on the ledger; it is the sum of all XRP in all accounts. However, you can use the API’s
ledgermethod with theaccountsoption to get the total XRP in the ledger (this includes all balances, but excludes XRP in the genesis account that was not issued). For a simpler method, the explorer shows the “Total XRP” on its main page. - Cross-check with multiple sources. To ensure accuracy, compare the data from the explorer with another independent source, such as the XRP Ledger’s own API or a different explorer like Bithomp. Discrepancies may indicate a data issue or a non-validated transaction.
Common Mistakes
- Using the wrong network. The XRP Ledger has a mainnet (livenet) and a testnet. If you use a testnet explorer, you won’t see mainnet transactions. Always ensure you are on the correct network.
- Misreading the amount. The explorer may show XRP in “drops” (the smallest unit) or in whole XRP. Double-check the unit before interpreting the value. 1,000,000 drops = 1 XRP.
- Confusing transaction hash with account address. A transaction hash is 64 hex characters; an account address starts with “r” and is about 34 characters. Searching for the wrong one will return no results.
- Not checking validation. A transaction that appears in the explorer but is not “Validated” is not final. It could be pending or have failed. Always wait for validation.
- Assuming total supply is a fixed number. The total XRP supply can decrease over time due to transaction fees being destroyed. It is not a static value; always check the current supply.
Tips
- Use the official explorer (livenet.xrpl.org) for the most reliable data, but cross-check with a second source for critical verifications.
- For programmatic verification, use the XRPL API. You can use tools like
curlto send requests. Example:curl -X POST https://s1.ripple.com:51234/ -H "Content-Type: application/json" -d '{"method":"tx","params":[{"transaction":"YOUR_HASH"}]}' - Understand that the “Total XRP” shown on explorers often excludes XRP in the genesis account (the original escrow) and may include XRP in escrow or other locked accounts. For the “circulating supply,” you may need to subtract XRP in escrow and the genesis account.
- When verifying a payment, always check the “Destination Tag” if one was used, as it is often required for exchange deposits.
Troubleshooting
- Transaction not found. If the explorer returns “Transaction not found,” double-check the hash for typos. If it’s correct, the transaction may not have been validated yet. Wait a few seconds and try again. If it still doesn’t appear, the transaction may have been rejected and never entered the ledger.
- Account not found. If an account address returns no results, it may be a new account that hasn’t been activated (it must have received at least the minimum reserve). Or you may be on the wrong network.
- API returns an error. If the JSON-RPC request fails, check that you are using the correct endpoint (mainnet:
s1.ripple.com:51234, testnet:s.altnet.rippletest.net:51234). Also ensure your request is properly formatted as JSON. - Discrepancy between sources. If two explorers show different balances, it may be due to one showing the “available” balance (minus reserves) and the other showing the total balance. Always look for the “balance” field in the API response, which is the total XRP in the account.
- Supply number seems off. The total supply can be confusing because it includes XRP in escrow (e.g., the 1 billion XRP monthly releases). To get the circulating supply, subtract escrow amounts and the genesis account balance. The official XRP Ledger site provides a breakdown.
Frequently Asked Questions
Can I verify a transaction without using a website?
Yes. You can use the public XRPL API directly with tools like curl or a programming language. The API returns the same data that explorers use, so you can verify independently.
What does “Validated” mean?
It means the transaction has been included in a ledger that has been accepted by the network through consensus. It is final and cannot be reversed. The ledger index and timestamp are also recorded.
Why does the total XRP supply change?
Each transaction destroys a small amount of XRP as a fee, so the total supply slowly decreases. Also, some XRP is held in escrow and released periodically, but the escrow balance is not considered “circulating” until released.
How do I check if an address has ever sent a transaction?
Search for the address in the explorer. The account page shows a “Transaction count” and lists recent transactions. You can also use the API’s account_tx method to get the full history.
What is the difference between the total supply and circulating supply?
Total supply includes all XRP that has been created, minus those destroyed as fees. Circulating supply excludes XRP in the genesis account (which is locked) and XRP in escrow. The circulating supply is what is actually available to the public.
Can I verify a transaction on a mobile device?
Yes. The official explorer works in mobile browsers. For API calls, you can use a mobile app that supports JSON requests, but it’s easier to use a desktop browser for that.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.