What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If an XRP transaction is missing, do not send it again immediately. First locate the transaction hash, confirm whether the server response has validated: true, read the final result code and metadata, and verify that the lookup server actually has the relevant ledger history. Then determine whether the apparent balance problem concerns native XRP, transaction fees and reserves, or an issued token held through a trust line.
A response such as txnNotFound is not proof that the transaction never happened. It may mean that the server lacks the required history, that the transaction has not yet reached its last eligible ledger, or that propagation is incomplete. The checks below separate those temporary conditions from a genuinely final outcome.
Start with the transaction hash and a validated result
The transaction hash is the unique identifier you need. Copy it from the wallet’s transaction details or, for a custodial transfer, from the exchange’s deposit or withdrawal record. An exchange’s status label is an internal record; it is not necessarily the same thing as an on-ledger transaction.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Query the hash through a trusted XRPL server or a reputable explorer that exposes the underlying XRPL response. Record these fields when they are available:
#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.
validated- the validated ledger index
- the transaction result code
- the affected account or accounts
- the transaction metadata
LastLedgerSequence, if the transaction includes it
The decisive checkpoint is validated: true. Results without that flag can be provisional, even when they contain a plausible result code. A transaction becomes final only after it is included in a validated ledger.
What the main result states mean
| Response or code | What it establishes | What to do next |
|---|---|---|
validated: true with tesSUCCESS |
The requested transaction succeeded in a validated ledger. | Use metadata and the affected account to reconcile the balance. |
validated: true with a tec code |
The transaction failed, but was applied to the ledger for its fee and may have other ledger effects. | Read metadata; do not assume that no XRP changed. |
No validated flag or validated: false |
The result is provisional or still being processed. | Wait, query again, and avoid submitting a duplicate payment. |
txnNotFound |
This server cannot find the transaction in the history available to it. | Check history coverage, ledger progress and the transaction’s last eligible ledger. |
Handle txnNotFound without creating a duplicate payment
XRPL servers do not all retain the same amount of ledger history. A server can follow the current ledger while storing only a limited range of older ledgers. Therefore, txnNotFound describes the server’s available history, not necessarily the network’s complete history.
Check the server’s history range
Inspect the server’s complete_ledgers value, or the equivalent history-coverage information it provides. Compare that range with the ledgers in which the transaction could have been included. If the range has a gap, the server cannot prove that the transaction is absent.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsUse another XRPL server with the required historical range, or wait if the gap is expected to fill. A current-ledger connection alone is not enough to investigate an older transaction.
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
Use LastLedgerSequence as the time limit
Many submitted transactions include LastLedgerSequence, the final ledger index in which they may be accepted. Absence is not final while the network has not yet validated that ledger. After the relevant last ledger is validated, you still need a server with continuous history across the possible inclusion range.
- Read the transaction’s
LastLedgerSequence, if present. - Check the server’s current validated ledger index.
- If the current index is lower, treat the missing result as provisional and wait.
- Once the current index has reached or passed the last eligible ledger, verify that the server has continuous history covering the relevant range.
- If history is incomplete, repeat the lookup on a server that has the missing ledgers.
- Only when the last eligible ledger is validated and the complete range has been checked can you treat the transaction as permanently absent.
Do not submit a second payment merely because one lookup returned txnNotFound. The original transaction could still validate later, producing two payments.
Read the final result code and metadata
For a validated transaction, tesSUCCESS is the result that means the requested operation succeeded. A different validated code means the operation did not succeed, but the balance effect depends on the code and metadata.
Why a failed transaction can still reduce XRP
Validated tec results are applied to a ledger even though the requested action fails. They consume the account sequence and destroy the transaction cost. The fee is not paid to the intended recipient. XRPL documentation describes these codes as transactions that did not succeed but were applied “to apply the transaction cost and may have had other side effects to the ledger.”
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
Consequently, a failed payment can reduce the sender’s XRP by the signed transaction Fee. The exact fee is the value in the transaction, not necessarily the standard minimum. The documented standard minimum is 10 drops, while network load can cause a higher fee. A validated transaction’s cost is irrevocably destroyed.
Inspect transaction metadata to determine what actually changed. Do not infer from a wallet’s simplified activity label that the only effect was a failed payment. Metadata can show account balance changes, sequence consumption and other ledger entries.
When no ledger inclusion means no shared-ledger change
If the transaction was never included in any validated ledger, it did not change shared XRPL balances. A local wallet may still display a pending deduction or reserved amount until it refreshes, and an exchange may maintain its own pending status, but those are not validated ledger effects.
Recommended Free Tools
Reconcile native XRP with the reserve requirement
The XRP shown as an account balance is not always fully spendable. XRPL requires a reserve for the account itself and for certain ledger objects it owns. The currently documented Mainnet values are a 1 XRP base reserve plus 0.2 XRP for each chargeable owned object. These are protocol parameters, not permanent guarantees; network fee voting can change them.
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
Calculate an account’s approximate reserve
- Call
account_infofor the account and recordOwnerCount. - Obtain the live base-reserve and owner-reserve values from
server_infoorserver_state. - Calculate: base reserve + (
OwnerCount× owner reserve). - Compare the result with the account’s current XRP balance and the amount the wallet marks as available.
Owned offers, escrows, trust lines and other ledger objects can contribute to OwnerCount. Sponsored entries and the first two trust lines have special rules, so a simple object count may not match every wallet’s display. Live server values are safer than an old help article or cached wallet estimate.
The reserve is not a separate wallet balance. It is a minimum amount that limits how much XRP can be sent or used to create additional objects. A transaction fee can still lower the account below its reserve requirement, and a reserve-parameter change can alter the amount that is available for a later outgoing transaction.
Common reserve-related explanations for an unexpected XRP amount
- The displayed balance includes XRP locked by the base or owner reserve.
- A trust line, offer, escrow or other owned object increased
OwnerCount. - A validated transaction charged a fee, including a fee higher than 10 drops during load.
- The wallet has not refreshed its spendable-balance calculation after a ledger update.
- Current network reserve parameters differ from the values hard-coded in the wallet interface.
Separate native XRP from issued tokens
XRPL accounts hold native XRP directly. Other currencies and tokens are represented through trust lines, so a token balance is not additional XRP and cannot be reconciled by looking only at the account’s native balance.
Check trust-line balances with account_lines
Use account_lines for the account and inspect each trust line’s currency, issuer and balance. The balance is expressed from the queried account’s perspective: a positive value means the account holds that issued asset, while a negative value means the account owes value on the line.
Trust-line balances can look surprising when a wallet groups several currencies together, rounds decimal amounts, or displays an issuer’s name instead of the currency and issuer pair. Compare the currency code and issuer as well as the numeric amount. A trust line can also contribute to reserve requirements even though its balance is not XRP.
Use the right ledger field for the question
| Question | Relevant check |
|---|---|
| How much native XRP is in the account? | Account balance from account information, then subtract the current reserve and any pending local display effects. |
| Why is less XRP spendable than the total? | OwnerCount, live reserve parameters and recent transaction fees. |
| Does the account hold an issued token? | account_lines, including currency, issuer and signed balance. |
| Did a transaction alter the account? | Validated transaction metadata and balance changes. |
A complete troubleshooting workflow
- Preserve the identifiers. Copy the transaction hash, sending and receiving account addresses, currency, amount and any displayed ledger index. Never share a secret recovery phrase or private key; public hashes and account addresses are sufficient for ledger lookup.
- Query more than one source when necessary. Start with a trusted server or explorer that exposes raw XRPL fields. If the result is missing, compare its history coverage with another server.
- Confirm finality. Require
validated: trueand identify the validated ledger. Treat an unvalidated response as provisional. - Interpret the code. Mark
tesSUCCESSas a successful requested operation. For a validatedtec, expect the fee and sequence consumption and inspect metadata for other effects. - Resolve a missing transaction. Check
LastLedgerSequence, the current validated ledger and continuous history. Wait or change servers when the transaction is still eligible or history is incomplete. - Reconcile XRP. Check the signed
Fee,OwnerCount, current reserve parameters and metadata balance changes. - Reconcile non-XRP assets. Query trust lines and match each currency with its issuer. Do not add issued-token amounts to native XRP.
- Contact the wallet or exchange only after the ledger facts are clear. Provide the public hash and account address, the validated ledger and result code, and the relevant metadata. Do not provide signing credentials.
Decision table for the most common cases
| Observed situation | Likely interpretation | Safe action |
|---|---|---|
Hash returns txnNotFound and the transaction’s last ledger is in the future |
The transaction may still validate. | Wait for that ledger range; do not resend. |
Hash returns txnNotFound, but the server’s history has a gap |
The server cannot establish absence. | Use a server with complete history or wait for the gap. |
Validated tesSUCCESS, but the recipient says nothing arrived |
The requested operation succeeded on-ledger; the recipient’s wallet or exchange may need to refresh or credit separately. | Share the validated hash and ledger with the recipient’s support channel. |
Validated tec and XRP is lower |
The requested operation failed, but the fee was destroyed and the sequence consumed. | Read metadata and the signed fee; do not expect the fee to be refunded. |
| Total XRP looks correct, but spendable XRP is lower | Reserve requirements or owned objects account for the difference. | Recalculate from live reserve values and OwnerCount. |
| A token amount is missing while XRP is unchanged | The issue concerns an issued asset or trust line, not native XRP. | Inspect account_lines and the currency/issuer pair. |
What not to conclude from a wallet screen
- A spinner, pending label or local deduction is not proof of validated ledger inclusion.
txnNotFoundfrom one server is not proof that the network rejected the transaction.- A failed requested payment is not proof that no XRP was spent; a validated
teccan consume the fee. - The displayed XRP balance is not automatically the amount available to send.
- An issued-token balance is not native XRP and should not be evaluated with the XRP reserve formula alone.
For a reliable diagnosis, anchor every conclusion to a validated ledger, a result code, history coverage and the relevant account fields. That combination distinguishes an unfinished lookup from a final failure and a real balance change from a reserve or token-display issue.
Quick Recap
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.
