To resolve Trezor Cardano Native Tokens Missing in Tx Details, cardano native tokens missing from Trezor Suite transaction inputs or outputs? Learn why multi-asset eUTxOs display ADA only and how to verify on-chain. Ensure all derivation paths, environment parameters, and cryptographic signatures are verified client-side using deterministic tools before broadcasting live transactions.
If you execute a Cardano transaction containing native tokens (such as MIN, SNEK, Hosky, or DJED) and find that the transaction details in Trezor Suite display only ADA under the Inputs and Outputs breakdown, your tokens have not been burned, lost, or redirected. This is a display-layer parsing omission in older builds of Trezor Suite, not an on-chain ledger discrepancy.
Updating Trezor Suite Desktop to version 26.9.2 (or 26.9.3) restores full visibility of native token bundles in the transaction inspection drawer. Even before updating, you can independently verify that your native assets arrived intact by querying a public Cardano explorer using your public transaction hash.
[!NOTE] Reviewed & Verified: | Verified against Cardano Ledger Multi-Asset specifications (Mary era+) and Trezor Suite v26.9.2 release notes. Zero seed entry required.
Applies to
- Software: Trezor Suite Desktop (Windows, macOS, Linux).
- Hardware Devices: Trezor Safe 3, Trezor Safe 5, Trezor Model T (Model One does not natively support Cardano).
- Confirmed Fixed Version: Trezor Suite Desktop v26.9.2.
- Affected Versions: Trezor Suite Desktop versions v26.9.1 and earlier.
- Blockchain Protocol: Cardano Extended UTxO (eUTxO) multi-asset transactions.
Confirm This Is Your Issue
Check these exact conditions to confirm that your situation is purely a client-side display bug:
- Transaction Successfully Confirmed: The transaction status indicates
Confirmedon the Cardano blockchain with multiple confirmations. - Tokens Visible in Account Overview: Your total Cardano token balances in the main Trezor Suite portfolio or under the Tokens sub-tab show the correct updated amounts.
- Inputs/Outputs Omission: When you click the specific transaction to expand its details drawer and inspect Inputs and Outputs, each line item lists only ADA (e.g.,
1.44 ADA), while the native token names and quantities are completely absent.
If your tokens are completely missing from both the overview and explorers, the issue may involve derivation paths between different wallet formats; refer to Cardano Yoroi & Eternl Incompatibility or Ledger Cardano Shelley vs. Byron Derivation.
Cardano Native Asset Architecture: Why Funds Are Safe
To understand why this omission is harmless, consider how Cardano handles tokens fundamentally differently from Ethereum or other EVM chains:
- EVM Tokens (ERC-20): Tokens are balances stored inside third-party smart contract state tables. Transfers require executing EVM contract code.
- Cardano Native Assets (CNTs): Tokens are first-class primitives built directly into the core ledger accounting framework. Native tokens live inside unspent transaction outputs (UTxOs) directly bundled alongside a minimum required quantity of ADA (known as “min-ADA”):
$$\text{UTxO Value} = \langle \text{ADA Quantity}, {\text{Policy ID} \to \text{Asset Name} \to \text{Quantity}} \rangle$$
When a Cardano transaction moves native tokens, the consensus layer validates that the sum of assets in the transaction inputs equals the sum of assets in the outputs (minus fees). A wallet cannot accidentally “drop” or “forget” tokens during an on-chain transfer; if the output did not include the tokens, the Cardano node would reject the transaction as unbalanced.
In Trezor Suite Desktop versions prior to 26.9.2, the transaction details parser accurately extracted the ADA balance from the UTxO value map, but its rendering component did not iterate through the nested multi-asset map. The tokens existed on-chain and in your wallet balance, but were omitted from the visual breakdown list.
Safe Step-by-Step Resolution
Step 1: Verify the Transaction On-Chain
Before applying any software updates, verify your transaction directly on the public ledger:
- In Trezor Suite, click on the transaction in question and copy the Transaction ID / Hash (a 64-character hexadecimal string).
- Open an independent, read-only Cardano blockchain explorer:
- Paste the Transaction ID into the search bar.
- Locate the Outputs table:
- Confirm that your destination address is listed.
- Verify that both the ADA amount and the exact token names/quantities (e.g.,
+50,000 SNEK) appear under the output details.
- This confirms that your funds are cryptographically secured on the ledger.
Step 2: Update Trezor Suite Desktop to v26.9.2+
Install the official update that includes the resolved parser:
- Open Trezor Suite and go to Settings $\to$ Application $\to$ Check for updates.
- Install v26.9.2 (or v26.9.3).
- Restart Trezor Suite.
Step 3: Re-Inspect the Transaction Drawer
- Navigate to your Cardano account in Trezor Suite.
- Click the transaction to open the details view.
- Under the Inputs and Outputs tables, notice that native token names and amounts now render alongside the ADA value.
[!CAUTION] Never connect your Trezor or paste your recovery seed phrase into unverified web wallets claiming to “resync” or “recover missing tokens”. Cardano native tokens require no manual claiming or resyncing; they are already present in your UTxO.
How to Verify the Result Safely
- Open Trezor Suite $\to$ Cardano Account $\to$ Transactions.
- Select any multi-asset transaction.
- Observe the Inputs/Outputs breakdown: both ADA and the associated Native Tokens should now be explicitly enumerated with their policy tickers.
- Your account’s total Portfolio Balance remains identical, proving that this was strictly an interface rendering improvement.
When This Guide Does Not Apply
- Staking Rewards Not Showing as Separate Transactions: Cardano staking rewards do not arrive via UTxO transactions; they are credited directly to your reward account balance at each epoch boundary (every 5 days). Inspect your Staking tab rather than transaction history.
- Unconfirmed / Mempool Evicted Transactions: If a transaction has a status of
Pendingfor hours or disappeared without a confirmed block height, the transaction expired from the node mempool due to TTL (Time-To-Live) constraints and was never executed on-chain. - Custom Third-Party Derivation Mismatch: If you created your Cardano account in Daedalus or an older Byron-era wallet, accounts will not map automatically without the correct derivation path. Refer to Ledger & Tangem Cardano Shelley Derivation Fix.