XRP wallet check · no wallet connection
Check your balance. Clarify where it came from.
Which of your purchases are still in this wallet? Reconcile your XRP balance with purchases, sales and transfers. Unresolved origin and missing data stay visible.
- Cost
- $0
- no sign-up needed
- Data source
- Validated ledger
- public XRPL nodes
- Connection
- None
- no wallet, no key
- Review record
- JSON
- save locally, load again
Quick guide
From the current balance to your records.
Here you connect one specific XRP wallet with your trading history. The check shows remaining purchase quantities and open gaps. Preparing complete tax reports across all accounts remains the job of your tax software.
View the wallet.
Enter the public address or open the example. You need no wallet connection and no key.
Reconcile the origin.
Load a CoinTracking CSV or enter your own acquisitions. Assign the account and review transfers. “FIFO” means that the oldest purchases are treated as used up first.
Take your review with you.
Resolve gaps and save the JSON review record. With the original CSV you can also prepare a file for your tax software; a wallet balance alone is not enough for that.
What do I need, and what remains my job?
For the balance, your public XRP address is enough. For the CSV reconciliation you need the complete CoinTracking transaction list with English column headers and the time zone used there. Export the list as a comma-separated CSV; do not save it as a PDF or Excel file.
You check whether all relevant accounts and transactions are included, which account belongs to the wallet and whether the records are correct. Our checks detect certain contradictions, but they confirm neither ownership nor completeness for tax purposes. A warning can also mean a transaction type that is not supported yet.
The CSV stays in your browser. A provider only receives it when you upload it there yourself. JSON is your working state that you can load again; a CSV is a transaction file, not a tax report. Save before you close or reload the page.
Try it with test data and verify the result
Our synthetic example contains eight transactions: two purchases, one partial sale, one transfer between your own accounts, and fees. Expected: 2,500 XRP in TEST_WALLET and 997 XRP in TEST_EXCHANGE. No real addresses or personal data. The example purchases have invented USD costs; no market conversion or tax figure is implied.
Open the example above, then “Import a file / continue” and “Load the synthetic test file”. The matching steps appear right in the import area.
At CoinTracking: “CSV Import”, not “Excel Import”. We know this from our own import preview of September 5, 2026, not from the provider documentation. Upload file 01 unchanged. All times in the test package are UTC, so choose UTC / GMT+0 for it. Before you confirm, check: eight transactions, separate quantity and date fields, no error messages. If you see whole rows in the type field, “Unknown type” or a date in 1970, cancel and check the import type and the file; do not change the dates of the transactions to make them fit.
Download the test package with expected values (ZIP, English notes, synthetic USD amounts)Detailed test procedure (in English)
For provider tests, use only separate, empty test accounts. The two positive files are alternative formats of the same transactions; do not import them together. Test the deliberately faulty file only here, locally. A successful import into a real CoinTracking account has not been confirmed yet.
Troubleshooting
If you get stuck with the reconciliation or the import.
The five questions that come up most often with the CSV import and the reconciliation.
Why does CoinTracking show “Unknown type” or the year 1970?
Which time zone do I have to enter?
Can I upload the CSV in addition to my API imports?
Why can I not simply add a transfer between my own accounts as a purchase?
Is a technically checked CSV a tax record?
For a detailed error analysis: balance discrepancies in CoinTracking. General rules are under XRP and taxes.
Method
What this check can do.
An incoming payment to a wallet is not yet a purchase. The check therefore separates public account data from your acquisition data.
Ledger data
Balance from a validated ledger. Incoming payments are read within fixed limits and, in the FIFO model, assigned to possible remaining holdings. Data gaps and failed side queries stay visible. The standard reserve is an estimate, not a binding amount you can withdraw.
Your entries
Acquisition date, cost and origin come from your records. They are not verified independently and not saved automatically. A transfer between your own wallets does not by itself create a new acquisition date.
A scenario, not a tax return
The calculation uses your entries and FIFO. Without a complete quantity reconciliation there is no simulation, and without cost basis or your tax rates there is no blanket $0 tax statement. Special cases belong in your complete records and, where needed, with a tax professional.
Sources: IRS digital assets, IRS Topic 409: capital gains and losses, IRS Form 8949 instructions and XRPL reserve parameters. Market price in the tool: Powered by CoinGecko. IRS sources and the XRPL reserve reference reviewed October 5, 2026; the tool reads the reserve itself from the ledger at each query.
If you continue somewhere else
If you want to continue somewhere else.
Limits and privacy
No tax, legal or investment advice. No check of wallet ownership, key security or a complete transaction history. The date of receipt and the market price are not records of your acquisition or cost basis. Calendar dates use UTC calendar days; you take the relevant acquisition day from your own records.
The public address is sent to our server and to public XRPL nodes. Acquisition data stays in the open session; downloads contain the data you entered. On request, only the address is remembered locally. Privacy