Loading the latest day…
The day in numbers
Transactions by type
Ranked by count. "Change" compares the day with the average of the 7 days before it. The small chart is the last 30 days (the chain's own daily counts where available, otherwise the days stored here).
| # | Type | Transactions | Share | Unique wallets | Change vs 7-day avg | Last 30 days |
|---|
How concentrated is each type?
The share of each type's transactions sent by its 1, 5 and 10 busiest wallets. A high share means a few wallets drive that number.
| Type | Top 1 | Top 5 | Top 10 | Busiest wallet |
|---|
Most active wallets
The 20 wallets that sent the most transactions. Addresses are shortened and link to the public block explorer. Labels appear only where the chain itself publishes a name (validators, contracts, organisations). The automation signal is a rule of thumb, not a judgement about anyone.
| # | Wallet | Transactions | Share of day | Main types | Public label | Automation signal |
|---|
Busiest contracts and assets moved
| # | Contract | Calls | Main functions | Public label |
|---|
| # | Asset | Transfer transactions |
|---|
Weekly net swap flows
For each token, the wallets that received the most and paid the most through decoded swap calls over the period, net. Amounts are in the token's own units. This is a record of past transfers only: it says nothing about why, and nothing about prices to come. Arbitrage and multi-step routes can make one wallet appear on both sides of different tokens.
Method
- Source. Every transaction of the UTC day (00:00–23:59 UTC; 01:00–00:59 UK summer time) from the chain's official public API, fetched once a day at about 00:20 UTC, one request at a time and no faster than 1 a second. The total is checked against the API's own count; a day that doesn't match is marked incomplete.
- Types. Each transaction is counted once, by its first contract type. Contract calls are split by the called function's name: swap or trade, add or remove liquidity, claim, ping (keep-alive) and other.
- Automation signal. A wallet is marked "likely automated" when two or more of these hold for the day: 100 or more transactions; active in 20 or more of the 24 hours; 95% or more of one type (with 30 or more transactions); very regular gaps between transactions. "Possible" means one holds. The toggle at the top removes "likely" wallets from the counts.
- Swap flows. Decoded from each successful swap call: what the wallet sent with the call, minus what the contract sent back to it. Calls that can't be decoded are left out, and the count is shown.
- Labels. Only names published on the chain: validator names from the official validator list, and the on-chain account names of contracts and organisations. Names that people give their own wallets are not shown.
- Limits. Counts measure activity, not value or adoption: a few automated wallets can make up most of a day. Data may be delayed or wrong.
Privacy
Everything here is public on-chain data that anyone can read in a block explorer. We shorten every address, we don't try to work out who is behind a wallet, and we don't combine this with any other data. If a label is wrong, or you'd like a wallet's label or row removed, email klevertrading2026@gmail.com.