An associated token account is the token account a wallet gets by default for one mint: its address is derived from the wallet, the token program and the mint under the Associated Token Account program. Because the address follows from those three inputs, you can check whether a token account belongs to a given wallet without asking RPC.
Derivation seeds#
The address is a program-derived address of the Associated Token Account program, ATokenGPvbdGVxr1b2hvZbsiqW5xWH25efTNsLJA8knL, with three seeds in this order:
- the wallet's address;
- the token program's address: SPL Token or Token-2022;
- the mint's address.
The token program is part of the seeds, so the same wallet and mint give a different ATA under Token-2022 than under SPL Token. Like any program-derived address it is off the Ed25519 curve, so no private key exists for it; base58 and public keys explains how that derivation works.
Create and CreateIdempotent#
| Instruction | Data | Behaviour |
|---|---|---|
| Create | empty, or the single byte 0 | creates the ATA and fails if it already exists |
| CreateIdempotent | the byte 1 | creates the ATA, or succeeds without change if it exists |
| RecoverNested | the byte 2 | recovers tokens sent to an ATA owned by another ATA |
The empty-data form of Create is easy to miss: a decoder matching only on the first byte will skip those calls. CreateIdempotent is common in swaps and transfers, where a client adds it in case the recipient's ATA does not exist yet. For Token-2022 mints the program also gives the new account the ImmutableOwner extension.
Mapping a token account to its owner#
- Take the token account address from the instruction.
- Collect candidate owners from the same transaction: its signers first, then the other non-program accounts.
- Take the mint, from the instruction if it names one, or from another instruction in the same transaction.
- Derive the ATA for each candidate with the mint and the token program the instruction called.
- A match proves the token account is that wallet's ATA for that mint. No match proves nothing; the account may simply not be an ATA.
The derivation runs forward only: from a token account address alone you cannot compute its owner, because it is a hash. Transactions usually contain the candidates you need.
How many token accounts are ATAs#
We derived the ATA for every distinct token account in two mainnet blocks on 18 November 2026, using the owner and mint the blocks record for each:
| Token program | ATAs | Not ATAs |
|---|---|---|
| SPL Token | 262 | 80 |
| Token-2022 | 470 | 39 |
| Total | 732 | 119 |
So 86% of the token accounts touched in those blocks were ATAs, which is why the mapping above resolves most wallet transfers.
Token accounts that are not ATAs#
The rest are ordinary token accounts at addresses chosen some other way: pool vaults owned by a program, temporary wrapped-SOL accounts created and closed inside one transaction, and accounts at program-derived addresses of their own design. For these the owner is in the account's data, not in its address, and you need account state or the instruction that created it to know who owns it.
Recognising ATAs in shred-decoded transactions#
From shreds you have the token account addresses, the signers and usually the mints, but no account data. The derivation turns those into ownership facts without RPC: this transfer went to that wallet's ATA. It is the cheapest way to attribute token transfers to wallets as they arrive, and it works for the token transfers recipe and for wallet alerts.
Questions about associated token accounts#
How is an associated token account address derived?#
As a program-derived address of the Associated Token Account program from three seeds: the wallet, the token program and the mint, in that order.
Is every token account an ATA?#
No. In our sample 86% were; vaults, temporary accounts and program-chosen addresses are not.
Why do SPL Token and Token-2022 give different ATAs?#
The token program is one of the seeds, so the same wallet and mint derive different addresses under each program.
What the derivation cannot do#
It confirms a guess; it cannot produce one. For a token account that is not an ATA it tells you nothing, and even for an ATA it says nothing about the balance, whether the account still exists or whether it was closed and recreated. Those are account-state questions that raw shreds do not answer. Token-2022 extensions add more state to consider.
Token accounts in practice#
The token program's instruction set shows what moves tokens between these accounts, and spotting new accounts uses the create instructions above. To attribute transfers on your own feed, decode a first transaction from raw shreds.
Sources#
- solana-program/associated-token-account interface/src/address.rs, commit fbf5379: seeds wallet, token program, mint (checked 2026-11-18)
- solana-program/associated-token-account interface/src/instruction.rs and program/src/processor.rs, commit fbf5379: Create (empty or 0), CreateIdempotent 1, RecoverNested 2 (checked 2026-11-18)
- @solana/kit 8.6.0 getProgramDerivedAddress, used to derive every ATA on this page (checked 2026-11-18)
- Mainnet getBlock slots 470,901,815 and 470,901,816: 851 distinct token accounts in postTokenBalances (checked 2026-11-18)
Raw shreds on your own server
Ultra Low Latency Shreds is $200 and Standard Shreds is $100. You pay in crypto, tell us which IPv4 address and UDP port should receive the stream, and we wire it up by hand.