“Supply” sounds like one number. On-chain, it is usually at least three different numbers, and conflating them is one of the most common ways a token’s scarcity or dilution gets misrepresented, sometimes deliberately, sometimes just carelessly.
Total supply, circulating supply, and max supply are different things
- Total supply – the number of tokens that currently exist, as recorded by the contract itself. For most standard tokens this is directly readable from the contract.
- Max supply – the hard cap a contract’s code enforces on how many tokens can ever exist, if one is coded in at all. Many tokens have no coded cap; “max supply” for those is a policy statement, not a contract guarantee, unless the code actually enforces it.
- Circulating supply – total supply minus tokens that are locked, held in treasury, unvested, or otherwise not freely tradable. Circulating supply is not a single on-chain value in most cases; it is calculated by someone (the project, a data aggregator) subtracting specific known-locked addresses from total supply, and that calculation is only as good as the list of addresses it accounts for.
The practical implication: total supply is usually the one hard, directly readable number. Max supply is only meaningful if you confirm the contract actually enforces a cap rather than just stating one in documentation. Circulating supply always depends on someone’s definition of which addresses to exclude, which means it is worth checking the methodology, not just the headline figure.
Step by step: reading supply from the contract
- Open the token contract’s address page and confirm the source is verified (see how to verify smart contract source code) so the Read Contract tab is decoded and readable.
- Call
totalSupply. Most token standards expose this directly; the raw number returned needs to be divided by ten raised to the power of the token’sdecimalsvalue (also readable from the same tab) to get the human-readable supply. - Look for a function that would indicate a hard cap being enforced in code (sometimes visible as a check inside a mint function, if the source is readable) rather than only trusting a cap mentioned in a whitepaper or website.
- Check whether a
mintfunction exists and who can call it. A contract with an active, callable mint function controlled by a single address or a small team means total supply is not fixed, regardless of what any current circulating-supply figure suggests. - For circulating supply claims, look at the explorer’s “Holders” tab to see the largest holding addresses, and check whether any of them are labeled as a known lock, vesting, or treasury contract – which lets you sanity-check a circulating-supply calculation yourself rather than taking the quoted figure on faith.
What on-chain supply data doesn’t prove
Reading totalSupply and decimals directly from the contract gives you a hard, current number. It does not tell you a project’s future minting plans beyond what the code itself enforces, does not tell you whether addresses excluded from a circulating-supply calculation are actually locked in a way that prevents them from moving, and does not tell you whether supply figures quoted on a third-party data site are using the same methodology the project itself uses. When a circulating-supply number matters to a decision, trace it back to the specific addresses being excluded and check those addresses yourself rather than accepting a dashboard figure as self-evidently correct.
Burns, vesting, and why the picture keeps moving
Total supply is not necessarily static even without active minting. Many tokens implement a “burn” mechanism that permanently destroys tokens, typically by sending them to an address with no known private key, which reduces total supply over time. Checking totalSupply at two different points and seeing a decrease is consistent with burning; checking documentation claims about a burn mechanism against whether the contract’s code actually calls a burn function anywhere is, as with minting, the difference between a policy statement and an enforced mechanic.
Vesting schedules complicate circulating-supply tracking in the opposite direction: tokens that already exist (counted in total supply) but are locked in a vesting contract that releases them gradually are not yet circulating, even though they will become so later on a schedule. Reading a vesting contract’s own release schedule, where the contract is verified and the schedule is encoded on-chain rather than only described in a document, gives you a forward-looking view of how circulating supply is likely to change, which is often more useful to a careful reader than a single current circulating-supply figure.
Not financial advice
This guide explains how to read supply figures directly from a token contract. It is general education, not financial, legal, or investment advice. Supply and dilution are only one factor among many in evaluating any asset, and this guide does not evaluate any specific token.
Why the same token can have different supply figures on different chains
Many tokens today exist as separate deployments across multiple chains, connected by a bridging mechanism rather than being a single contract. In that situation, reading totalSupply on one chain’s deployment only tells you the supply on that specific chain – the token’s combined supply across every chain it’s deployed on requires checking each deployment separately and adding them together, and a claim about “total supply” that only cites one chain’s figure for a genuinely multi-chain token is incomplete. Confirming how many chains a token is actually deployed on, usually disclosed in the project’s own documentation, is a necessary first step before any cross-chain supply figure can be checked properly.
A simple but common mistake: forgetting decimals
The raw integer returned by totalSupply is not the human-readable figure – it has to be divided by ten raised to the token’s decimals value, which is also readable from the same Read Contract tab. Skipping this step produces a number that’s off by many orders of magnitude, and misreading a raw contract value as the actual supply is a surprisingly common error even among people checking the chain directly rather than trusting a secondhand figure.
FAQ
Why do different websites sometimes show different circulating supply numbers for the same token?
Because circulating supply is a calculated figure, not a single on-chain value, and different data providers can use different lists of addresses they treat as locked or non-circulating. Total supply, by contrast, should match everywhere since it reads directly from the contract.
Does “max supply” always mean the contract can’t create more tokens?
Only if the cap is actually enforced in the contract’s code. A stated max supply in marketing materials with no corresponding enforced check in the mint function is a claim, not a guarantee.
How do I check if a token’s mint function is still active?
Read the verified contract’s source for a function that increases total supply, and check what access control (an owner check, a role check) restricts who can call it. If that access has genuinely been removed on-chain (see how to check if contract ownership is renounced), minting by that path is closed; if not, it remains possible.
Can I check supply for tokens on non-EVM chains the same way?
The underlying idea is the same – supply is a property the chain’s own ledger tracks – but the specific tool differs. Solana token supply, for example, is read through Solana’s own explorers and token program conventions rather than an EVM-style Read Contract tab.
Not financial advice. Human-edited; AI-assisted drafting is disclosed in our editorial guidelines. Spotted an error? See how corrections work.



