How to Check Token Balances on Different Networks in Talisman

Understanding Talisman's Multi-Chain Address Recognition

1. Talisman wallet treats each blockchain as an independent ledger layer, yet maintains a unified interface for address management across networks like Polkadot, Kusama, Ethereum, and Moonbeam.

2. A single public address may represent different assets on different chains—such as DOT on Polkadot Relay Chain versus USDC on Moonbeam EVM—due to distinct token standards and contract deployments.

3. The wallet automatically detects chain-specific address formats during import: SS58 for Substrate-based chains and 0x-prefixed hexadecimal for EVM-compatible ones.

4. Users must manually select the correct network before viewing balances, as Talisman does not auto-scan all supported chains simultaneously for privacy and performance reasons.

5. Imported addresses appear under “Watched Accounts” with customizable labels, enabling side-by-side comparison of holdings across heterogeneous ecosystems.

Step-by-Step Balance Verification via Built-in Explorer

1. Launch Talisman and navigate to the “Accounts” tab, then tap the “+” icon to add a new watched address.

2. Paste the target address into the input field and confirm its validity; Talisman will display recognized chain compatibility icons beside the entry.

3. Select one specific network from the dropdown list—e.g., Polkadot, Astar, or Shiden—and proceed to load the account view.

4. Upon loading, the interface renders native token balance alongside any known fungible tokens deployed on that chain’s token registry.

5. Scroll down to reveal transaction history and smart contract interactions, including transfers, staking actions, and dApp approvals tied exclusively to that chain context.

Manual Token Addition for Non-Standard Assets

1. Some tokens—especially newly launched or non-registered ERC-20 or SPL tokens—do not appear automatically in the asset list.

2. Tap the “Add Token” button within the selected network’s asset view and choose “Custom Token.”

3. Enter the full contract address, token name, symbol, and decimal precision as verified from official project documentation or trusted block explorers like Subscan or Etherscan.

4. Confirm addition; the token will now be displayed with real-time balance updates synced directly from on-chain state.

5. Repeating this process per network ensures consistent visibility of cross-chain positions without relying on third-party indexing services.

Exporting and Cross-Referencing On-Chain Data

1. Each address page includes a “View on Explorer” link that opens the corresponding block explorer in an embedded browser window.

2. This allows users to inspect raw balance entries, verify token ownership via contract call traces, and validate multisig configurations if applicable.

3. Transaction timestamps are rendered in UTC and include block height, confirming finality status according to the consensus rules of the underlying chain.

4. Export options include copying raw JSON-RPC responses or downloading CSV-formatted transaction logs for offline reconciliation.

5. For auditors or compliance teams, these exports serve as immutable evidence of asset custody and movement patterns across disparate ledgers.

Frequently Asked Questions

Q: Can Talisman display balances for the same address across multiple chains at once?No. Talisman requires explicit network selection for each balance query. It does not aggregate balances across chains into a single fiat-valued total.

Q: Why does a token appear on Etherscan but not in Talisman’s asset list for Ethereum?The token may lack metadata registration in Talisman’s internal token list or use a non-standard implementation that prevents automatic detection.

Q: Is it safe to import someone else’s public address into Talisman?Yes. Importing a public address grants read-only access to on-chain data. No private keys or signing capability is involved.

Q: Does Talisman support viewing NFT holdings across different standards?Yes. For Ethereum, it displays ERC-721 and ERC-1155 tokens. For Polkadot-based chains, it shows assets conforming to the RMRK standard when enabled in settings.