SOCI4L

Addresses per L1

How many distinct addresses actually send on an Avalanche L1, read from each chain's own blocks.

Sampled Aug 23, 2026

The finding

Transaction counts say how much a chain does. They do not say how many people it does it for.

Median L1

8

distinct senders found

Under 25 senders

22 of 27

81% of the chains measured

Between one and five

12

the whole chain, all week

These are counts of distinct addresses seen sending, drawn from blocks spread across each chain's history rather than from one recent minute. A chain can process millions of transactions and still be four addresses; several here do. That is not a criticism of any of them, and some are settlement rails where a handful of signers is the design. It is only what the ecosystem looks like when the question is asked out loud.

The distribution

Every mainnet L1 the sampler could reach on Aug 23, 2026.

  • None found1

    tomatochain

  • 1 to 512

    Andromeda, Blockticity, even, FIFA Blockchain, Hashfire, Innovo Markets Mainnet L1, Kula, Loyal, north-investments, Space L1, technical-ivory-gopher, UPTN

  • 6 to 249

    Dexalot L1, DFK L1, Dinari Financial Network, Orange, PLAYA3ULL GAMES L1, StraitsX L1, The Grotto, TixChain, Turing Chain

  • 25 to 593

    Beam L1, Blaze, Henesys

  • 60 or more2

    Avalanche (C-Chain), Gunz L1

What the numbers are, and are not

The limits belong next to the figures, not in a footnote.

The top band is open. Sampling stops at 60 senders, so the 2 chains reported there have at least that many and an unknown true figure. They are never folded into a band that implies a ceiling.

Unreachable chains are excluded. A chain whose endpoint returned nothing is left out rather than counted as zero: no reading is not a reading of none. 27 chains were actually read.

It is a sample, not a census. Blocks are read at a stride across each chain's history, so a chain with more senders than we saw is possible. The direction of that error is one way: the real counts can only be higher, never lower.

A count is not a share. Below 25 senders we publish no automated percentage anywhere on the site, because a share drawn from three addresses describes those three and not the chain. The L1 table shows the count instead, per chain.

Automated means busy, not fake. Where a share is published it counts senders with 100,000 or more lifetime transactions on that chain. A high figure means the traffic is concentrated in heavy addresses. It does not say who they are or why.

Go deeper