C-Chain activity
Every figure covers the last 30 complete days and is compared with the 30 before it. The newest day the upstream has published is excluded, because it is still being written and always looks like a collapse.
Chart
Transactions included in blocks that day.
Staking
The Primary Network validator set and the stake behind it, as the metrics API reports it. These are levels rather than totals, so a change compares the latest reading with the one thirty days before it.
- Validators
- 577
- Delegators
- 28,451
- Self stake
- 168.17M AVAX
- Total stake
- 203.34M AVAX
Self stake plus delegated
Avalanche L1s
Every L1 ranked by transactions over the last 30 days, with its share of all tracked L1 activity.
31 L1s with activity in the last 30 days, through 2026-10-09
| # | Behaviour | Tx / sender | Automated | ||||
|---|---|---|---|---|---|---|---|
| 1 | 16.22M | 45.1% | No comparison yet | SteadyBroad | 3.1 | 60 seen | |
| 2 | 8.78M | 24.4% | No comparison yet | SteadyMixed | 13.6 | 15% | |
| 3 | 5.62M | 15.6% | No comparison yet | SteadyConcentrated | 1094 | 20 seen | |
| 4 | 3.99M | 11.1% | No comparison yet | SteadyMixed | 6.9 | 92% | |
| 5 | 567.5K | 1.6% | No comparison yet | SteadyMixed | 41.7 | 10 seen | |
| 6 | 181.8K | 0.5% | No comparison yet | SteadyConcentrated | 351 | 9 seen | |
| 7 | 151.1K | 0.4% | No comparison yet | SteadyBroad | 1.3 | 13 seen | |
| 8 | 101.8K | 0.3% | No comparison yet | Regular | — | — | |
| 9 | 84.7K | 0.2% | No comparison yet | IntermittentConcentrated | 1728 | 3 seen | |
| 10 | 80.0K | 0.2% | No comparison yet | RegularConcentrated | 316 | 4 seen | |
| 11 | 61.3K | 0.2% | No comparison yet | SteadyBroad | 3.8 | 3% | |
| 12 | 55.1K | 0.2% | No comparison yet | SteadyBroad | 3.0 | 21 seen | |
| 13 | 43.8K | 0.1% | No comparison yet | SteadyMixed | 9.5 | 9 seen | |
| 14 | 7.6K | <0.1% | No comparison yet | SteadyBroad | 4.4 | 3 seen | |
| 15 | 5.8K | <0.1% | No comparison yet | SteadyBroad | 1.4 | 22 seen | |
| 16 | 5.3K | <0.1% | No comparison yet | RegularMixed | 35.8 | 6 seen | |
| 17 | 4.1K | <0.1% | No comparison yet | Steady | — | 0% | |
| 18 | 2.4K | <0.1% | No comparison yet | SteadyBroad | 1.7 | 2 seen | |
| 19 | 1.8K | <0.1% | No comparison yet | SteadyBroad | 1.5 | 23 seen | |
| 20 | 1.7K | <0.1% | No comparison yet | SteadyBroad | 1.9 | 22 seen | |
| 21 | 1.2K | <0.1% | No comparison yet | IntermittentMixed | 54.1 | — | |
| 22 | 502 | <0.1% | No comparison yet | Steady | — | 2 seen | |
| 23 | 423 | <0.1% | No comparison yet | SteadyBroad | 2.6 | — | |
| 24 | 238 | <0.1% | No comparison yet | IntermittentMixed | 14.0 | 2 seen | |
| 25 | 163 | <0.1% | No comparison yet | Regular | — | — | |
| 26 | 146 | <0.1% | No comparison yet | Regular | — | 19 seen | |
| 27 | 49.0 | <0.1% | No comparison yet | IntermittentBroad | 1.5 | 7 seen | |
| 28 | 33.0 | <0.1% | No comparison yet | IntermittentBroad | 1.4 | — | |
| 29 | 14.0 | <0.1% | No comparison yet | IntermittentBroad | 1.1 | — | |
| 30 | 7.0 | <0.1% | No comparison yet | Intermittent | — | 9 seen | |
| 31 | 5.0 | <0.1% | No comparison yet | IntermittentBroad | 1.0 | — |
Ranked from the daily series each chain reports to the public Avalanche metrics API. The automated column reads as a count where a chain has too few senders for a share. "3 seen" means three distinct addresses across blocks spread over that chain's whole history, which is the chain rather than a failed reading, and is why no percentage is offered for it. Tx per sender divides the window's transactions by the sender count the upstream reports: a high number means the activity sits in few hands, a low one that it is spread across many. It says how concentrated a chain's traffic is, not who is behind it. It is blank where the upstream reports fewer transactions than senders, which happens on the quieter chains and leaves the two series without a shared denominator to divide. The automated column is ours: we sample senders out of recent blocks and ask each chain how many transactions those addresses have ever sent, then report the share at or above 100,000. Because the sample comes from blocks it is weighted by activity, so it describes a chain's traffic rather than its user base. It is left blank unless the sample covers at least a tenth of a percent of that chain's daily senders: below that the same measurement taken twice does not agree with itself, so there is nothing honest to print. The C-Chain, with roughly 176,000 senders a day, sits under that line.
Reputation layer
Our own data, and the part no explorer can produce: where scored wallets sit on the ladder, and what the four dimensions behind the score average out to.
- Profiles scored
- 38
- Median score
- 10.5
- Verified humans
- 3
- Mean confidence
- 0.48
Wallets with a current reputation score
Passed on-chain human verification
How much of the signal set the engine had
Tier ladder
- Legendary100+00.0%
- Elite50+00.0%
- Established25+513.2%
- Rising10+1642.1%
- Newcomer5+1744.7%
- Starter0+00.0%
38 scored profiles, placed by their current score. Bands are the same ones a profile is awarded.
S4 vector, averaged
confidence 0.48- Humanity13.2
How much says a person, not a script · 12 of 38 at zero
- Activity32.1
Depth and recency of on-chain use
- Social0.5
Verified accounts and the follow graph · 32 of 38 at zero
- Economic33.5
Value moved and gas actually paid · 15 of 38 at zero
Each dimension runs 0 to 100. Confidence is the engine's own report of how much of its signal set it had: signal classes we do not collect yet are not scored as zero, their weight is renormalised away and the gap is reported here instead.
Sources and method
Network figures come from the public Avalanche metrics API at metrics.avax.network, read as daily series. Weekly and monthly buckets on this page are aggregated here from those days rather than taken from the upstream rollup, which understates part of the C-Chain history. The specifics of that defect, and the second index we check against, are on the transactions page.
Staking comes from the same API’s Primary Network series. The L1 table's tx per sender is that table's own arithmetic on the same snapshot: transactions in the window divided by distinct senders in it. It measures concentration, not legitimacy, and is not a reputation figure.
The automated column is ours and comes from a different method again: once a week we pull senders out of each chain's recent blocks and ask that chain how many transactions each of those addresses has ever sent, then report the share at or above 100,000. Because the sample is drawn from blocks it is weighted by activity, so it describes traffic rather than head count, and it is rounded to whole percent because a sample of around sixty addresses does not support a decimal place. A chain we cannot reach, or cannot draw 25 senders from, is left blank.
The reputation section is ours too, computed from the score snapshots behind every SOCI4L profile. It is deliberately not projected onto the L1 table: those on-chain signals are a C-Chain cache filled in for addresses we have been asked about, so a per-chain share of genuine users drawn from it would be a self-selected sample wearing a percentage. The two datasets are shown side by side, not multiplied.
The network series on this page are downloadable without a key. The chart is /api/avalanche/metrics?metric=txCount&format=csv, the L1 table is /api/avalanche/l1s?format=csv with every column it draws, and the staking series are at /api/avalanche/validators. The sibling pages publish their own downloads with their own methodology.
The reputation section is the exception, and deliberately: what is on this page is the whole of it, the aggregate. Per-profile scores are answered by the reputation API one address at a time, which is a different thing from a file of everyone.