What is the total supply of XAN?

Anoma's tokenomics page gives XAN a fixed supply of 10 billion tokens. On Ethereum, this explorer adds up every mint and burn the token contract has recorded and checks the result against the contract's totalSupply(). The live comparison is on Proof.

Where does the XAN price on this site come from?

The current price and its 24-hour change come from CoinGecko, with DefiLlama as a fallback, and the daily chart comes from DefiLlama's history for the same coin. Unlike the supply and the balances, the price is not read from the chain or checked against it.

When does locked XAN unlock?

Anoma's Governance V2 post says balances locked under the first version of governance vest linearly over three years from 29 September 2026 at 12:00 UTC, and can be claimed as they vest. The tokenomics page separately describes a 12-month lock-up followed by 36 months of linear unlocking for four of the genesis groups. The vesting window the token contract reports is on Governance.

How many XAN holders are there?

The live count is on XAN: addresses holding XAN on either network, each counted once, with a separate count for each network. An address is not a person, since one exchange wallet can hold XAN for many customers and one person can use several addresses.

How does this explorer treat XAN on BNB Chain?

It reads a XAN token contract on BNB Chain and counts it separately, from its own transfers and its own totalSupply(), in its own section of XAN. The headline supply is the Ethereum contract's, where XAN launched. The Anoma pages this guide cites do not describe how XAN reaches BNB Chain, so this guide does not say.

Is this Anoma's official explorer?

No. Gnoma Explorer is independent and not affiliated with the Anoma Foundation or Heliax; Anoma's official explorer is explorer.anoma.net. How the two differ is covered in Gnoma and explorer.anoma.net.

Guide · updated 2026-10-24

XAN, Anoma's token: what it is and how it is counted

What the XAN token is for, what Anoma says about its supply, genesis allocation and vesting, and how this explorer builds a ledger of every holder from the token's own transfers and checks it against the contract. Live figures are on the XAN page; this guide explains where they come from.

What XAN is for

XAN is Anoma's native token. Anoma's tokenomics page says it can be used for payments, transaction fees and network governance, and the launch post calls it the coordination mechanism for the Anoma ecosystem. That post, dated 29 September 2025, announced the token as live on Ethereum mainnet, with Anoma's first governance system launching alongside it. Holders can manage XAN in the Anoma Portal or in any ERC-20 compatible wallet (ERC-20 is the common token standard on Ethereum). AnomaPay, a payments network built on Anoma for paying privately onchain, lists XAN among the tokens it supports. Putting XAN into AnomaPay is what this explorer calls a shield, which AnomaPay's docs call a deposit; shields and unshields of XAN appear on Shielded pool like those of any other token. [1] [2] [3] [4]

Fixed supply and genesis allocation

Anoma's tokenomics page gives XAN a fixed supply of 10,000,000,000 tokens. It divides that supply at genesis (when the token was created) among five groups, restated in the table below. The page says the shares of the Anoma Foundation, R&D and ecosystem, backers and core contributors are subject to a 12-month lock-up, and that they then unlock linearly over the following 36 months. This explorer does not turn that schedule into an unlocked or circulating amount. It shows only what the token contract itself records. [1]

Group, as Anoma names it	Share at genesis	What it is for, in brief	In the lock-up list
Community, Marketing, and Liquidity	25%	Incentives for the community, market presence and rewards for public contributors	No
R&D & Ecosystem	19%	Ongoing research and development, ecosystem growth and the network's long-term sustainability	Yes: 12 months, then linear over 36 months
Anoma Foundation	10%	The Foundation's operations and long-term sustainability	Yes: 12 months, then linear over 36 months
Backers	31%	Institutional backers and angels from Anoma's past fundraising rounds	Yes: 12 months, then linear over 36 months
Core Contributors	15%	Core contributors to the Anoma network and protocol suite	Yes: 12 months, then linear over 36 months

Locked balances and vesting

Under the first version of Anoma governance, holders locked XAN to vote, and the weight of a vote followed the amount locked. Anoma's Governance V2 announcement, dated 16 September 2026, says balances locked under that first version now vest linearly over three years, starting 29 September 2026 at 12:00 UTC, and that holders can claim whatever has vested at any time. Locked tokens can still vote: voting power counts the whole balance, vested or not. The same post says the timelock (the contract that holds a passed proposal for a waiting period before it takes effect) controls the XAN token and is the only thing that can change it. The tokenomics page and the Governance V2 post describe their schedules in different terms, and this guide states each as written without combining them. The Governance page reads the vesting window and the token's owner straight from the XAN contract; how proposals and votes work is in the governance guide. [1] [2] [3]

The XAN contracts this explorer reads

Network	XAN token contract
Ethereum	0xcedbea37c8872c4171259cdfd5255cb8923cf8e7
BNB Chain	0x7427bd9542e64d1ac207a540cfce194b7390a07f

XAN launched on Ethereum mainnet. The explorer reads the token contract there and a XAN token contract on BNB Chain, each in the same way: its own Transfer logs, its own balances and its own totalSupply(). The headline supply on XAN is the Ethereum contract's. The BNB Chain contract's supply is shown in its own section and is not added to it. The headline holder count is addresses holding XAN on either network, each counted once, and every network also has its own count. The Anoma pages cited in this guide do not describe how XAN reaches BNB Chain, so this guide does not describe it either. [1]

How the ledger is built from every transfer

Every time XAN moves, the token contract records a Transfer log: who sent it, who received it and how much. The explorer reads every one of these logs the contract has ever emitted from Etherscan's log index and applies them in chain order, oldest first.
It reads only blocks a set number of confirmations behind the newest one, so a transfer in a block that is later replaced (a reorg) is not counted.
Each transfer moves its amount from the sender's balance to the recipient's. A transfer from the zero address creates tokens (a mint), and one to the zero address destroys them (a burn). The ledger's own supply is every mint minus every burn.
Each page of transfers is written in one step together with the position it reached, so a page counts exactly once, whatever fails around it. If a transfer would take a balance below zero, an earlier transfer must be missing, and the ledger stops instead of guessing.
Beside each balance it keeps the address's first and last activity and its transfer counts, plus daily totals, first-time holders, flows into and out of tagged exchange wallets, and every transfer of a million XAN or more.

How the ledger is checked against the contract

Supply: once the ledger has reached the newest confirmed block, its mints minus burns are compared with the contract's totalSupply() at the same block, every tenth minute and on every run until the two match. Equal means no mint or burn was missed or counted twice.
A second source: a transfer between two holders leaves the supply unchanged, so the supply check cannot see a missing one. On each run once the ledger has caught up, its Transfer logs for newly finalized blocks are compared with the logs an ordinary RPC node of the network returns for the same blocks, a second source separate from Etherscan. A transfer the ledger lacks is added. One the node does not have is never removed automatically: the same blocks are asked again, and the operator is alerted if the difference persists.
Balances: every hour, on each network, the three largest holders and five randomly chosen holders have their ledger balance compared with the contract's balanceOf() at the ledger's own block, read from an ordinary node. Where no node still serves that block, today's balance is read instead and every transfer since that block is undone.
Exchanges: every hour, each tagged exchange's change in holdings over the last 30 days is compared with its deposits minus its withdrawals.
A disagreement must show up in three checks in a row before it is reported as a mismatch. A ledger that is still catching up, or has stopped following the chain, is not sampled. Every result, with the time it was read, is on Proof and at /api/v2/proof.

Holders, concentration and exchange flows

A holder here is an address with a balance above zero. An address is not a person: one exchange wallet can hold XAN for many customers, and one person can use many addresses. For each network, XAN shows the supply and whether it matches the contract, the holders and transfers read, the share held by the largest 10 and 100 addresses, the fewest addresses that together hold more than half the supply, and a concentration score (the Gini coefficient) from 0, everyone holds the same, to 1, one address holds everything. It charts transfers, XAN moved, addresses holding XAN and first-time holders over time, sorts holders into size classes and lists the largest. Addresses with a public name tag, a label for a known exchange wallet, bridge or DEX pool, are grouped to show where tagged supply sits. Exchange flows count XAN sent to a tagged exchange wallet or deposit address from outside that exchange as in, and the reverse as out. Moves between one exchange's own wallets are not counted, and an untagged wallet such as cold storage counts as outside, so a move there shows as out. The figures are recomputed from the ledger every five minutes.

XAN For each network: supply and its check, holders, concentration, where tagged supply sits, exchange flows and large transfers; plus the current price and the daily price chart.

Where the price comes from, and what this page is not

The price is the one figure on XAN that does not come from the chain. The current price and its 24-hour change come from CoinGecko's public price service, refreshed about every five minutes; when CoinGecko refuses a request, DefiLlama's price service for the same coin is used instead. The daily closing-price chart comes from DefiLlama's daily history for the same coin. Neither is checked on-chain the way the supply is. The market value shown under the total supply is the Ethereum supply multiplied by today's price, so it counts every token, locked or not, and is not a circulating market cap. The page does not estimate circulating supply or unlocks, does not name who is behind an address beyond its public name tag, and is not trading or investment advice. Trading on decentralized exchanges is on Ecosystem, computed on Dune Analytics. For comparison, on 24 October 2026 Anoma's official explorer at explorer.anoma.net showed the XAN price, 24-hour change, market rank, market cap and 24-hour volume on its dashboard, credited to CoinGecko with a link, which puts more market data and its source in one view. Its Contracts page listed the Protocol Adapter on each network and no XAN token contract, and neither page showed holders or supply. [1] [2]

Open data and the API

Everything on XAN can be downloaded or queried free, with no key and no sign-up. Developers lists the open data files: every XAN transfer on Ethereum and on BNB Chain since the token began, one gzipped CSV file per month, and a list of every holder on each network, all with exact decimal amounts. A manifest gives each file's rows, size, SHA-256 checksum and the block it runs to. The API serves the page's figures at /api/v2/xan, large transfers at /api/v2/xan/transfers, every transfer after a given block at /api/v2/xan/feed (it keeps the last eight days), and one address's XAN history on one network at /api/v2/address/{address}/xan, also as CSV. The current price is in /api/v2/overview. Code and data are under the MIT licence; when showing figures from here, credit Gnoma Explorer with a link.

Questions

What is the total supply of XAN?: Anoma's tokenomics page gives XAN a fixed supply of 10 billion tokens. On Ethereum, this explorer adds up every mint and burn the token contract has recorded and checks the result against the contract's totalSupply(). The live comparison is on Proof.
Where does the XAN price on this site come from?: The current price and its 24-hour change come from CoinGecko, with DefiLlama as a fallback, and the daily chart comes from DefiLlama's history for the same coin. Unlike the supply and the balances, the price is not read from the chain or checked against it.
When does locked XAN unlock?: Anoma's Governance V2 post says balances locked under the first version of governance vest linearly over three years from 29 September 2026 at 12:00 UTC, and can be claimed as they vest. The tokenomics page separately describes a 12-month lock-up followed by 36 months of linear unlocking for four of the genesis groups. The vesting window the token contract reports is on Governance.
How many XAN holders are there?: The live count is on XAN: addresses holding XAN on either network, each counted once, with a separate count for each network. An address is not a person, since one exchange wallet can hold XAN for many customers and one person can use several addresses.
How does this explorer treat XAN on BNB Chain?: It reads a XAN token contract on BNB Chain and counts it separately, from its own transfers and its own totalSupply(), in its own section of XAN. The headline supply is the Ethereum contract's, where XAN launched. The Anoma pages this guide cites do not describe how XAN reaches BNB Chain, so this guide does not say.
Is this Anoma's official explorer?: No. Gnoma Explorer is independent and not affiliated with the Anoma Foundation or Heliax; Anoma's official explorer is explorer.anoma.net. How the two differ is covered in Gnoma and explorer.anoma.net.

Sources

Gnoma Explorer is independent and not affiliated with the Anoma Foundation or Heliax. Statements about Anoma are Anoma's own, from the sources above; figures are this explorer's, from the pages linked in the text.