Blockpit automatically imports Tron transactions via your public wallet address (public key): all common transaction types (Deposits, Withdrawals, Trades, etc.), all tokens (TRC10 + TRC20) & NFTs (TRC721 + TRC1155) as well as alle Synced Balances.
DeFi stands for Decentralized Finance and enables the transfer and trading of crypto assets within one or more decentralized networks (blockchains). With Blockpit you can import these transactions into an integration for your tax & portfolio tracking.
Import method: wallet address (public key)
How to add your Tron integration
All you need is your public wallet address (public key) from Tron. Here is how:
1️⃣ Open + Integration (or, in the Dashboard, click + Integration on the tab Integrations).
2️⃣ Select the tab Blockchain and then Tron.
3️⃣ Enter a name for the integration and paste your public key (public wallet address) from Tron.
4️⃣ Select the import time span.
💡 Tip: Keep Full History as the preset import time span. Choosing a specific start date only makes sense if you want to add transactions that lie before it manually.
5️⃣ To finish, click Continue. Blockpit creates the integration and imports the asset balance and transactions automatically.
What happens after you add it
After Continue, Blockpit imports the Tron integration automatically. This is what applies afterwards:
Where you see the result: in the Dashboard on the tab
Integrations(holdings and balance) and under Transactions (individual transactions)Synchronization: transactions are synchronized fully automatically once a day (Blockpit Plus subscription required); this takes a few minutes to hours. With
Sync Allor per integration in the Dashboard (tabIntegrations) you can trigger it yourselfBalance: The Synced Balance and live prices are updated automatically every 7 minutes, without a sync. If the Synced Balance and the calculated balance differ, Blockpit shows the tip
Mismatched Balance
Blockpit records these Tron transactions automatically
General
✅ All common transaction types (Deposits, Withdrawals, Trades, etc.)
✅ All tokens (TRC10 + TRC20) & NFTs (TRC721 + TRC1155)
✅ All Synced Balances
Supported protocols (dApps)
✅ JustLend (incl. energy rentals)
✅ Sunswap (all versions)
✅ SocialSwap
✅ JustSwap
Swaps (Trades)
A swap is the exchange of one crypto asset for another. These exchanges are usually recognized automatically with the label Trade.
✅ Supported
NFTs (TRC721 + TRC1155)
Inflows and outflows of so-called Non-Fungible Tokens (NFTs) in your integration are usually recognized automatically with the label Trade or Airdrop, or as unlabeled deposit/withdrawal. Your NFT assets are generated completely dynamically from your public key in our database.
The following NFT transactions and dApps are supported:
✅ Mints
✅ Claims
✅ Transfers
✅ Trades
Liquidity Providing/Mining
Providing crypto assets in so-called liquidity pools is shown as several swaps or transactions with the label Trade. The crypto assets you provide are exchanged in equal parts for a so-called LP token. From then on, this LP token represents your share of the respective liquidity pool. As soon as you leave the pool again, it is swapped back.
✅ Supported
Staking, Lending, Airdrop & Bounty Rewards
If generated income is imported automatically as unlabeled Deposit, you can categorize the affected transactions afterwards with the appropriate transaction label (Staking, Interest, Airdrop, Bounty, etc.), as shown in the image below.
✅ Supported
💡 Tip: You can give free NFT mints the label Airdrop. You recognize them by the transaction note Fallback_Claim.
How do I solve problems with my Tron integration?
Should transactions still be missing or imported incorrectly, or should your Synced Balance be displayed incompletely, you can help our support team to include them (if technically possible) in our import spectrum.
Please send us the following via chat request:
all available information about the problem
your public wallet address (public key)
the corresponding transaction hash from TronScan
Typical mistakes
✗ Swap appears as unlabeled deposit and withdrawal → connect both transactions afterwards (instructions in the section Swaps)
✗ Liquidity transaction appears as unlabeled deposit and withdrawal → recreate it afterwards (instructions in the section Liquidity Providing)
✗ Income arrives as unlabeled deposit → categorize it afterwards with the appropriate label (Staking, Interest, Airdrop, Bounty)
✗ Free NFT mint is not labeled → give it the label Airdrop; recognizable by the transaction note Fallback_Claim
✗ Missing transaction reported without naming public key and transaction hash → both belong in the chat request