TL;DR: Duplicate transactions in CoinTracking typically result from importing the same data twice or from conflicting transaction IDs. These duplicates can block transfers from matching correctly and distort your portfolio. Use the Duplicate Filter and careful manual review to identify and fix them.
What causes duplicate transactions?
Importing the same exchange or wallet file/API multiple times
Using multiple sources for the same account (e.g., API + CSV)
Conflicting or repeated transaction IDs from exchange exports
These situations can prevent one side of a transfer from being imported or cause trades to appear twice.
How do duplicates affect transfers?
If one side of a transfer (deposit or withdrawal) is flagged as a duplicate, CoinTracking may skip importing it altogether. This results in unmatched transfers, even when the data seems complete.
Example: You import 0.5 BTC withdrawal twice but only one matching deposit—CoinTracking may discard one withdrawal and show a missing or mismatched transfer.
How can I fix duplicate transactions?
Simply press the big orange button saying “delete all duplicates” or:
Enable the Duplicate Filter: CoinTracking flags potential duplicates.
Manually review and remove extra entries.
Manually add skipped transactions that weren’t imported due to duplicate ID conflicts.
Check import logs to identify which file/API created the duplicate.
Can I prevent duplicates in the future?
Yes. To reduce risk:
Stick to one import method per account (e.g., API or CSV, not both)
Review new data carefully when importing in bulk
Use comments or trade groups to track import sources
Summary
Duplicates often go unnoticed until they cause transfer issues or tax reporting problems. Review flagged duplicates regularly and streamline your import methods to maintain clean, accurate records.