Solana Account Decoder

Solana account decoder

This Solana account decoder reads any account from mainnet. You get the owner, lamports, size and rent status, then the data decoded: token accounts and mints natively, Anchor accounts with the program’s on-chain IDL, and a hex dump for everything else.

No sign-up. Runs in your browser. Last reviewed November 4, 2026 by the Builderz team.

How it works

What is fetched

One getAccountInfo call at confirmed commitment, with the data as base64. The server returns a summary, never the raw RPC reply. The rent-exempt minimum for the account’s size comes from the same RPC node.

Native token layouts

Accounts owned by the Token or Token-2022 program are read by fixed layout. A mint is 82 bytes: mint authority, supply, decimals, initialized flag, freeze authority. A token account is 165 bytes: mint, owner, amount, delegate, state, native reserve, delegated amount, close authority. Token-2022 accounts with extensions list the extension types found after the base layout.

How Anchor accounts are matched

Anchor writes an 8 byte discriminator at the start of each account. The server fetches the owner program’s IDL, compares those 8 bytes with each account type in it, and on a match decodes the rest with Borsh using the IDL layout. Programs without a published IDL are not decoded.

What raw means

No known layout matched. You see the account’s first 8 bytes as hex, which is the Anchor discriminator if there is one, and a hex dump of the first 256 bytes. Large arrays in decoded output show their first 200 items.

Privacy and caching

Only the address you paste is sent to our server, which asks a Solana RPC node for it. Our code keeps nothing but a per-address rate-limit counter. Results are cached for about 30 seconds, and lookups are limited to 10 per minute per visitor.

Questions about this tool

Why does my Anchor account show as raw?

The program may not publish an IDL on chain, or the IDL does not list this account type. Many teams keep the IDL off chain. Paste the IDL into the Anchor IDL inspector to read the layout, then decode by hand.

The discriminator matched but decoding failed. Why?

The on-chain IDL can be older than the deployed program, so the layout no longer fits the bytes. The error names the byte offset and the type where reading stopped.

Why are amounts shown in raw units?

Token amounts and supply are stored as integers. Divide by 10 to the power of the mint’s decimals to get the display amount.

Does it work on devnet or testnet?

No. This tool reads mainnet only. An address that exists only on another cluster shows as no account.