How it works

A token launcher. Each launch creates a token and a trading pool for it, locks the pool's money so it cannot be pulled, and splits the pool's swap fees between the token's fee recipients and the platform (Clanker itself).

A launch is one call to a Clanker factory that creates a new token (with a fixed supply, usually 100 billion) and its pool. Every token here was launched that way.

A generation of Clanker's contracts, each with its own fee rules. Older (v0 to v3.1) launch on Uniswap V3 pools and pay the platform a share of the pool fee. All v4 (v4.0 and v4.1) launch on Uniswap v4 pools with Clanker's hook, which adds the platform's 20% fee on top. A v4 token's version is set by the locker it launched with. See "Clanker versions in one minute" above.

The Clanker contract that creates tokens and their pools. Each version has its own factory on each chain. On v4 it also receives the platform's swept fees, which the team then withdraws.

The trading market for one token against its paired asset, on Uniswap (a decentralized exchange where anyone can trade). Volume and trades here count only each token's own Clanker pool, the one created at launch.

What a token trades against in its pool, usually WETH (ETH in token form). Volume and fees are measured in it, then converted to US dollars at that day's price.

The Clanker contract that holds a pool's liquidity (the money traders trade against) so nobody can pull it, and collects its fees. On older versions fees wait in the pool position the locker holds until someone claims them; on v4 a separate fee locker holds each recipient's credited fees until they withdraw.

On v4, a contract attached to every Clanker pool. It charges the platform's 20% fee on each trade, can make the pool fee dynamic, and runs launch protection.

Pools others created with Clanker's v4 hook without launching through Clanker. They pay the platform fee (v4), so they count in fee totals under All and All v4, but they are not launches and their trading is not in volume.

The platform's wallets, controlled by the Clanker team and listed in this site's contract registry: two team Safes (shared wallets that need several team members to sign), the team fee recipients set in each factory, and the CLANKER buyback treasury. Fees paid to them count as Platform revenue.

The wallets that share a token's pool fees. On v4, up to seven chosen at launch, each in a reward slot (a place in the token's list of fee recipients, with a share set at launch): the creator, the launch app, other recipients the creator added, and sometimes the platform. On older versions the locker sets the split at launch: the creator, the platform and on v3.1 the launch app (on v2 and v3 a launch partner can get part of the platform's share).

• Creator: the wallet that launched the token (on v4, the first fee recipient that is not one of Clanker's own wallets or a known launch app).
• Launch app: the app or bot it was launched through: its share on v3.1, and on v4 the slot a known launch app takes (Bankr, Clank.fun, Clawnch). An app not on that list counts as Creator or Other recipient, by its slot. The clanker.world app's share goes to Clanker's own wallets, so it counts as the platform.
• Other recipient: anyone else, such as a co-creator or community wallet on v4, or a launch partner's part of the team share on v2 and v3.

On v4, when a recipient asked to be paid in one token, Clanker's locker swaps the fees it collected in the other token automatically. These swaps are not counted as volume or trades, but the fees they pay count in trading fees.

The swap fee a Clanker pool charges on every trade, usually 1%. LP stands for liquidity provider (someone whose money is in the pool for traders to trade against). Clanker locks the pool's liquidity, so these fees go to the token's fee recipients.

Example: a $1,000 trade at 1% pays $10.

On v4, a static pool fee is a fixed rate. A dynamic fee moves with trading, often higher right after a launch. Older versions use a fixed Uniswap V3 tier, 1% on almost every token.

On v4 pools, an extra 20% of the pool fee charged by Clanker's hook on top of every trade, taken in the paired asset and earned by the platform.

Example: a $1,000 trade with a 1% pool fee pays $10 to the fee recipients plus $2 to the platform.

The platform's cut of the pool fees on versions before v4, which have no separate platform fee. The platform takes a part of each claim of pool fees: 50% to 75% on v0 depending on the token (most 60%), 60% on v1 to v3 (the creator gets 40%) and 20% on v3.1. On v2 and v3 tokens with an override wallet, a launch partner gets part of that 60% and only the platform's part counts. It is paid in both tokens of the pool, WETH and the token itself.

Everything traders paid in swap fees: the pool fee plus the platform fee (v4) on top. Fees paid by fee-conversion swaps count too. This is what traders paid, not what the platform earned (see Platform revenue).

How recipients get paid.

• Credited (v4): fees added to a recipient's balance in Clanker's fee locker when the locker collects them, at a later swap, so credits can trail the trades.
• Claimed (older versions): fees collected from the pool in one go and split between the creator, the platform, on v3.1 the launch app and on some v2/v3 tokens a launch partner, so they appear in bursts on the claim day.

Pool fees credited or claimed for the wallets that launched the tokens: their share of each older-version claim, and on v4 the first reward slot not paid to Clanker's own wallets or a known launch app. Sniper auction payouts are counted apart.

What creators, launch apps and other recipients were paid from pool fees, on the day each was credited or claimed. It does not add up to Trading fees: on older versions a claim can pay out months of fees at once. The platform's own share is in Platform revenue, and sniper auction payouts are not included.

What the platform (Clanker) earned, counted when it was earned and valued that day: its v4 fee, fee shares paid to Clanker's own wallets, its share of sniper auction bids, presale fees, and fees on the team's own CLANKER/WETH liquidity, minus refunds to creators.

Fees earned by the Clanker team's own liquidity (money it put in the pool) in the CLANKER/WETH pool, held in a team locker. Counted in Platform revenue, but not as a fee share of any version, so it shows only under All versions.

Token balances creators took back from the platform. On older versions part of the platform's fee share was paid in each token itself and held in Clanker's team Safes. Creators can take their own token's balance back through Clanker's refund contract (ClankerSafeErc20Spender), proving they are the creator. Each withdrawal is subtracted from Platform revenue that day, valued at the token's average trading price. Clanker's fee sink moving the platform's own WETH and CLANKER out of the Safes through the same contract is not a refund.

Example: BNKR's creator has taken back about 667M BNKR this way.

Launch protection on some v4 tokens: right after a launch, bots bid in WETH for the right to make the first trades instead of racing for them. 20% of the winning bid goes to Clanker's factory and 80% to the token's fee recipients by their shares. 43 auctions in 2026 ran on pools that are not Clanker launches; neither their 80% payouts nor the factory's 20% are counted.

DefiLlama and Dune are public crypto data sites. DefiLlama counts WETH as it lands in four of Clanker's own wallets, so it leaves out fees paid in tokens, does not subtract refunds and can include transfers that are not fees. Dune and clanker.world's homepage count Clanker tokens traded on every pool, not only Clanker's own, so their volume is much larger.

Money moving after it was earned, not new revenue: withdrawals, sweeps, team withdrawals, the fee sink's pulls from the team Safes, and its CLANKER buybacks and USDC conversions. Shown apart and never added to revenue, because the same money was already counted when it was earned.

On v4, a recipient moving their credited fees out of Clanker's fee locker into their own wallet. One withdrawal takes the whole balance in one currency, from every token that paid it.

Platform fees (v4) moved out of Clanker's hook to its factory. It happens at a later swap of any pool with the same paired asset, so it trails the fees a little.

The Clanker team taking swept fees and the platform's share of sniper auctions out of the factory.

Clanker's fee sink (a contract that spends revenue) moving the platform's own WETH and CLANKER fee shares out of Clanker's team Safes before swapping them. A move between Clanker's own wallets, not a refund.

CLANKER that Clanker's fee sink bought with WETH from the platform's revenue on Base. CLANKER the sink already held from fee shares is not counted as bought.

USDC (a dollar stablecoin) that Clanker's fee sink bought with WETH (and sometimes CLANKER) from the platform's revenue on Base. Since late April 2026 everything the sink swaps goes to USDC.

Optional features chosen at launch.

• Vault: part of the supply locked in a Clanker contract and released to the creator after a set time (v3.1 and v4).
• Airdrop: part of the supply set aside for a list of wallets to claim (v4).
• Dev buy: the creator buys some of the token in the launch transaction (v3.1 and v4).
• Presale: the token is sold for ETH before it launches, and the platform takes a fee on the ETH raised (v4).

On v4, the first seconds after a launch are protected from bots: by a short trading delay, a fee that starts high and falls, or a sniper auction.

The app, bot or SDK (a developer toolkit) a token was launched through, as the launcher recorded it. Spellings of the same source are merged; launches that record none show as Direct / not recorded.

The social network where someone asked a bot to launch the token, such as Farcaster or X. Launches from the website or SDK usually have none.

Swaps sent by Clanker's own lockers, the fee-conversion swaps. They are stored but left out of volume and trade counts, so nothing is counted twice; the fees they pay still count.

• Volume: the dollar value of buys and sells on Clanker's own pools.
• Trades: how many buys and sells (one swap is one trade).
• Average trade: volume divided by trades.

• Tokens traded: how many different tokens had at least one trade.
• Top token share: the share of volume from the single biggest token, which shows how much one token drives the totals.

• Market cap: price times total supply.
• Liquidity: the money in a token's pools that traders buy from and sell into.
• Holders: wallets holding the token. All three come from Codex (a market data provider) for each chain's 100 most traded tokens; a market cap shows only with at least $1,000 of liquidity and at most 1,000 times it.

How an amount paid in a Clanker token is valued: what buyers paid divided by tokens traded on its pool that day (a volume-weighted average price), or the latest of the 30 days before with real trading (at least 0.001 of the paired asset). With no real trading, the amount counts as $0.

Every amount is converted to US dollars at its asset's price on the UTC day it happened, so history does not change when prices move. Today uses a running price updated every 5 minutes.

Images, descriptions, links, launch apps and verified badges come from clanker.world, which keeps them for every launch. v4 launches also record most of them onchain.

The badge clanker.world shows on tokens its team has verified.

clanker.world's curated list of notable tokens. clanker.world can give them their own logo in place of the one set at launch.

• Thin liquidity: market cap hidden because the pool is too thin to trust.
• Not tracked: Codex has no data yet (it covers the 100 most traded tokens per chain).
• No USD price: no price that day.
• Not recorded: the launch did not record it.
• No token qualifies: no token passes the $1,000 liquidity rule.

• UTC day: a day from 00:00 to 24:00 UTC.
• Today so far: today's UTC day up to now, still growing.
• Last 24 hours: a rolling window that ends at the current hour. On 1D, volume and trades use the last 24 hours, while fees, revenue and launches use today so far.

A block is a batch of transactions a chain adds every few seconds. Data through is the time of the last block read; everything up to then is counted.

How far the newest block read is behind now. New blocks are read every 2 minutes, so 1 to 4 minutes is normal; over 10 minutes the pages say the chain is behind.

Reading a chain's past from its first Clanker launch: launches and fees, then every trade, then on v4 the platform's exact fee on every swap. Until it finishes, lifetime numbers for that chain are lower than the real ones and a notice says so.

Events (records the contracts write onchain) kept with their raw data because something they need (usually the token's launch) was not stored yet. They are read again every night and placed once possible, so nothing is dropped.