Blockpit automatically imports Polkadot transactions via your public wallet address (public key): all common transaction types (incl. Transfers, Staking, etc.), all kinds of extrinsics as well as cross-chain transfers of DOT. Not recorded: 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 Polkadot integration
All you need is your public wallet address (public key) from Polkadot. Here is how:
1️⃣ Open + Integration (or, in the Dashboard, click + Integration on the tab Integrations).
2️⃣ Select the tab Blockchain and then Polkadot.
3️⃣ Enter a name for the integration and paste your public key (public wallet address) from Polkadot.
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 Polkadot 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 Polkadot transactions automatically
General
✅ All common transaction types (incl. Transfers, Staking, etc.)
✅ All kinds of extrinsics
✅ Cross-chain transfers of DOT
⛔ Synced Balances
❗ Polkadot (legacy) migration to Polkadot Asset Hub
Due to the migration to Polkadot Asset Hub, the Synced Balance is permanently disabled (0). In addition, new transactions from the migration date onwards are only available via Polkadot Asset Hub Integration.
For this reason, Polkadot (legacy) Integrations show a mismatched balance. To fix this, the existing calculated DOT balance from the old Polkadot (legacy) Integration must be transferred to the new Polkadot Asset Hub Integration on the migration date using a manually created Transfer.
Swaps (Trades)
A swap is the exchange of one crypto asset for another. These exchanges are usually recognized automatically with the label Trade.
✅ 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 Polkadot Asset Hub 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 subscan.io
Typical mistakes
✗ Swap appears as unlabeled deposit and withdrawal → connect both transactions afterwards (instructions in the section Swaps)
✗ 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