Start with the transaction hash, then check whether the result is validated: true. A validated tesSUCCESS is final success; a validated failure code is final failure, although some failures still consume a fee. If the server returns txnNotFound, that usually describes the server’s available ledger history—not proof that the transaction never existed. Only after checking ledger coverage, LastLedgerSequence, fees, reserves and trust-line balances should you decide that funds are actually missing.
1. Collect the identifiers before changing anything
Use the transaction hash shown in your wallet’s activity details. A hash is the exact identifier needed to inspect an XRPL transaction. Also record the sending account, destination account, asset (native XRP or an issued token), amount, time shown by the wallet and any displayed fee or status.
As an Amazon Associate I earn from qualifying purchases.
If an exchange or other custodial service initiated the transfer, save its withdrawal or deposit record as well. A service’s internal status is not the same thing as an on-ledger transaction. An exchange can show “processing” before it submits a transaction, or show a completed internal record while the network transaction is still being located.
Free tools Windows power users keep installed
One-click scans. No signup required.
Do not provide a secret recovery phrase, private key or signing credential to anyone offering help. Public transaction hashes and account addresses are sufficient for ledger verification.
#1 Best Overall
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
2. Look up the transaction and check finality
Query the hash through a trusted XRPL server or a reputable explorer that exposes the underlying API response. The decisive field is validated.
- Open the transaction details and copy the complete hash, without changing its capitalization or characters.
- Inspect the API response for
validated: true. - For a validated result, record the validated ledger index, the result code, the affected accounts and the transaction metadata.
- If
validatedis absent or false, treat the response as provisional. Keep monitoring rather than declaring success or failure.
XRPL reaches agreement in ledgers. Once a ledger is validated, its contents are immutable under the normal consensus rules. A transaction that never appears in a validated ledger cannot have changed shared ledger balances. A response from a server that has not yet caught up, however, can be incomplete.
What the result codes mean
| Validated result | Meaning | Balance implication |
|---|---|---|
tesSUCCESS |
The requested transaction succeeded. | Apply the metadata to see the delivered amount and affected objects. |
A tec code |
The requested action failed, but the transaction was applied to a ledger. | The signed transaction fee is destroyed and the sequence is consumed; other side effects are possible. |
| Any other validated failure code | The transaction’s final outcome is failure. | Read metadata rather than assuming that no field changed. |
| No validated result | The outcome is not final, or this server cannot yet show it. | Do not resubmit or treat the balance as settled. |
Only a validated tesSUCCESS proves that the requested payment or other operation succeeded. A validated failure is still a confirmed ledger event, while an unvalidated response is not a final verdict.
3. Treat txnNotFound as a history question
txnNotFound means the server cannot find the transaction in the history it currently has available. It does not, by itself, prove that the transaction was never submitted or will never validate. XRPL servers differ in how many historical ledgers they retain: a server can follow the current ledger while lacking older ranges.
Rank #2
- Proven security at scale: Over 9 years and millions of cards issued with no known remote hacks, while military‑grade EAL6+ security keeps your private keys locked inside the chip. Your cryptocurrencies stay strongly protected from online attackers.
- Tap once to manage your entire crypto wallet across 90 blockchains - no USB cables or Bluetooth, no batteries, no setup. Access 14,100+ coins & tokens, DeFi, NFTs, and staking instantly from your phone
- Smart backup: Use your second Tangem Wallet as your Backup keys with end‑to‑end encryption; no more papers, pictures. If one card is lost, the remaining can still restore full access, with an optional seed phrase available for advanced users.
- Engineered to last up to 25 years: Waterproof (IP69K), shockproof and tested for extreme temperatures from −25°C to 50°C. A durable cold wallet with long‑term protection and independently audited security.
- Trusted by 6 million users worldwide - buy, sell, swap, stake, and spend cryptocurrency directly. The secure offline storage wallet designed for how people actually use crypto wallets
Check the server’s coverage
Inspect the server’s complete_ledgers value, or the equivalent history-coverage information. It should include every ledger range in which the transaction could have been included. A gap means the server cannot answer the question reliably.
- If the server’s history begins after the transaction’s possible inclusion range, query another server with fuller history.
- If there is a temporary gap, wait for the server to acquire the missing ledgers and query again.
- If the transaction is recent, allow time for propagation and validation before interpreting absence.
Use LastLedgerSequence to establish a deadline
Many submitted transactions include LastLedgerSequence, the last ledger in which they are eligible for inclusion. Check whether that ledger has itself been validated. If the network has not reached the stated sequence, the transaction can still appear later and its absence remains provisional.
After the last eligible ledger is validated, absence can support a conclusion that the transaction did not enter a validated ledger—but only when the lookup server has continuous history across the full eligible range. If the server is missing any part of that range, switch to a server with the required history instead of declaring the payment lost.
4. Do not submit a second payment just because a lookup failed
A provisional “not found” response is one of the easiest ways to create a duplicate payment. The original submission may still propagate or validate after the first server failed to locate it. Before resubmitting, verify all of the following:
Rank #3
- Unparalleled Security: Protect your assets with EAL 6+ Secure Element, offering robust defense and complete transparency
- Simple & Secure Interface: Manage your digital assets easily with a clear OLED screen for secure on-device confirmations
- Supports 1000s of Coins & Tokens: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet
- Effortless Asset Management: Monitor and transact seamlessly with Trezor Suite, our intuitive desktop and mobile app
- Enhanced Backup Solution: Multi-share Backup eliminates single points of failure for secure cold wallet recovery
- The original hash has been checked on more than one suitable server or explorer.
- The server’s history covers the relevant ledgers continuously.
- The transaction’s
LastLedgerSequence, if present, has passed in a validated ledger. - No validated result already shows success or a fee-consuming failure.
- An exchange or custodian has confirmed that it did not submit the transfer under another record.
If you cannot establish those facts, keep the original hash and investigate rather than sending again.
5. Read metadata when a transaction is validated
The result code alone is not a complete balance explanation. Open the validated transaction’s metadata and identify which accounts, trust lines and ledger objects changed. For a payment, confirm the delivered amount and destination-side effects rather than relying only on the amount originally entered.
Why a failed transaction can still reduce XRP
A validated tec result means the requested action failed, but XRPL applied the transaction to charge its cost and may have made other ledger changes. The official documentation describes these codes as transactions that “did not succeed, but it was applied to a ledger to apply the transaction cost and may have had other side effects to the ledger.” The transaction cost is irrevocably destroyed, not paid to the intended recipient, and the account sequence is consumed.
Recommended Free Tools
The standard minimum transaction cost documented for XRPL is 10 drops (0.00001 XRP). The exact signed Fee is charged when the transaction is included, and it can be higher than the minimum when the network is under load. A failed payment therefore can leave the sender with less XRP even though the recipient did not receive the requested payment.
Rank #4
- UNPARALLELED SECURITY: Protect your assets with Trezor Safe 5's NDA-free EAL 6+ Secure Element, offering robust defense and complete transparency.
- EFFORTLESS NAVIGATION: Experience seamless crypto management with the vibrant color touchscreen, designed for intuitive and user-friendly interactions.
- ENHANCED USER EXPERIENCE: Enjoy tactile confirmation with Trezor Touch Haptic Engine, making each interaction precise and engaging.
- SUPPORTS 1000s OF COINS & TOKENS: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet.
- EASY ASSET MANAGEMENT: Monitor and transact seamlessly with Trezor Suite, our user-friendly desktop and mobile app
6. Check whether the XRP reserve explains the “missing” spendable amount
An account’s displayed XRP balance is not always the amount it can send. XRPL requires a reserve to protect the ledger from unlimited account objects. Current documented Mainnet values are a 1 XRP base reserve plus 0.2 XRP for each chargeable owned object. These network parameters can change through protocol fee voting, so use live server values rather than treating the figures as permanent.
Calculate the reserve from live account data
- Call
account_infofor the account and recordOwnerCount. - Call
server_infoorserver_stateand read the current base and incremental reserve values. - Calculate the required reserve as base reserve + (
OwnerCount× owner reserve). - Compare that requirement with the account’s XRP balance and the transaction’s fee.
Owned offers, escrows, trust lines and other ledger objects can increase OwnerCount. Sponsored entries and special rules for the first two trust lines can change how individual objects are counted, so a simple object count from a wallet screen may not exactly match the server calculation.
The reserve is not a separate wallet or locked sub-account. It is a minimum-balance rule that limits how much XRP is available for sending or for creating additional objects. Fees can still reduce the account below its reserve requirement, and a reserve-parameter change can alter the amount a wallet labels as spendable.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →7. Separate native XRP from issued-token balances
First identify the asset denomination in the unexpected balance. Native XRP is held directly by the account. Issued currencies and tokens are represented through trust lines; they are not extra XRP and cannot be interpreted with the native XRP balance field.
Inspect trust-line balances
- Call
account_linesfor the account. - Find the relevant currency and issuer.
- Read the trust-line balance from the queried account’s perspective.
- Interpret a positive balance as value held by that account and a negative balance as value the account owes.
A wallet may aggregate issued assets, hide issuer details or display a token beside XRP, which can make the total look inconsistent. Verify the currency code, issuer and trust-line entry before concluding that XRP disappeared. Trust lines are also ledger objects and can contribute to the account’s reserve requirement.
8. Diagnose common scenarios
| What you see | Most likely explanation | Next action |
|---|---|---|
txnNotFound on one server |
That server lacks the relevant history or has not caught up. | Check complete_ledgers, then use a server with continuous coverage. |
No result and LastLedgerSequence has not passed |
The transaction is still eligible or propagating. | Wait and monitor; do not duplicate-submit. |
Validated tesSUCCESS, but the amount looks different |
Delivered amount, fee or destination-side metadata differs from the wallet’s initial display. | Read the validated metadata and compare both account balances. |
Validated tec and lower XRP |
The requested action failed, but the fee was destroyed and the sequence consumed. | Record the exact code, Fee and metadata; the fee is not refundable. |
| XRP balance present but less is spendable | Reserve requirements or a recent fee reduce available XRP. | Recalculate reserve with live server values and OwnerCount. |
| Unexpected non-XRP asset | An issued-token trust-line balance is being shown alongside XRP. | Use account_lines and verify currency and issuer. |
9. When to contact a wallet or exchange
Contact the service that initiated the transaction after you have preserved the hash, result code, validated ledger, server history range and metadata. Ask for its internal withdrawal or deposit identifier and whether it submitted a different hash. Give support public account and transaction identifiers only.
If a transaction is validated, the ledger result takes precedence over a stale wallet label. The service may need to refresh its indexer or reconcile a custodial record. If no transaction can be found after the eligibility deadline and a full-history server confirms the range, ask the initiating service to investigate its submission process rather than sending another payment yourself.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteQuick Recap
10. A compact verification checklist
- Copy the exact transaction hash.
- Check
validated: trueand the result code. - Record the validated ledger and inspect metadata.
- For
txnNotFound, inspectcomplete_ledgersand history gaps. - Check
LastLedgerSequencebefore deciding that absence is final. - Never duplicate-submit while the original outcome is provisional.
- For lower XRP, review the signed
Fee, current reserve values andOwnerCount. - For another asset, inspect
account_lines, currency and issuer. - Share only public identifiers when escalating.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
