Token Accounts Explained: Structure and Fields

A token account is where your SPL token balance actually lives on Solana. Unlike your wallet's SOL balance, which sits in your main system account, each SPL token balance requires its own account owned by the Token Program. When you open an explorer and click a token holding, you are looking at one of these accounts.

The five fields you will see everywhere

Standard token accounts contain five fields that appear consistently across explorers, CLI tools, and program documentation:

1. Mint

The address of the mint account that defines which token type this account holds. A single wallet may have multiple token accounts for the same mint (unusual but valid) and many accounts for different mints.

2. Owner

The address authorised to transfer tokens out of this account. Usually this is your wallet address. Programs can also own token accounts — for example, a staking pool's treasury.

3. Amount

The raw token balance stored on-chain. Divide by the mint's decimal count for human-readable values. This field updates with every transfer, mint, or burn affecting the account.

4. Delegate and delegated amount

A delegate is a secondary address permitted to transfer up to a specified limit without the owner's signature on each transfer. The delegated amount caps how much the delegate can move. Many readers first encounter delegates in DeFi approvals; the on-chain representation is these two fields.

Setting a delegate requires owner action. Revoking a delegate sets the delegate field back to null. During our workshops, this is the section that generates the most questions — keep our glossary entry on delegates handy.

5. Close authority

The address allowed to close the account and reclaim its rent-exempt SOL reserve. By default, the owner is also the close authority. Closing an empty token account returns the small SOL deposit to the close authority.

How token accounts relate to your wallet

Your wallet address does not directly contain token balances. Instead, your wallet controls token accounts where the owner field matches your address. Wallets scan the chain for token accounts owned by you and aggregate them into the portfolio view.

When you receive tokens for the first time, the sender's transaction often creates a new token account for you — unless an associated token account already exists.

Rent exemption

Every token account occupies on-chain storage and must hold enough SOL to be rent-exempt. The exact threshold is small (on the order of fractions of a cent at typical SOL prices) but non-zero. Accounts below the threshold may be garbage-collected; in practice, wallets and programs fund the exempt minimum when creating accounts.

Reading a token account on an explorer

1. Find the transaction that created or last modified the account.
2. Open the account page and confirm the mint address matches the token you expect.
3. Check owner matches the wallet you control.
4. Verify amount using the mint's decimals.
5. Note any active delegate before signing approval transactions elsewhere.

When things go wrong

Transfer failed — "account not found": The recipient may lack a token account for that mint. The sender or recipient must create one first.

Balance shows zero but transaction succeeded: You may be looking at a different token account for the same mint, or viewing raw amount without adjusting decimals.

Unexpected delegate: Review recent approval transactions. Revoke delegates you no longer trust through your wallet or a direct Token Program instruction.

Continue with Associated Token Accounts or book a workshop seat for guided explorer practice.