Komodo address activity at a glance
On-chain snapshot of holder behaviour: who is active, where the supply sits, and how long it has been sleeping.
Active addresses 30 / 90 / 365 days
An address counts as active if it transacted at least once inside the window. Bars show address counts, the line shows the KMD balance those addresses currently hold.
Active addresses & balance held
Transactions per window
Active vs. dormant — addresses (365d)
Active vs. dormant — supply (365d)
Supply distribution balance buckets
How many addresses sit in each balance band — and how much of the tracked supply each band controls.
Addresses vs. supply share by bucket
Supply share by bucket
Lorenz curve — holder inequality
Concentration
Dormancy waves time since last transaction
Each band groups addresses by how long ago they last moved funds. Comparing the share of addresses against the share of supply separates dust from meaningful idle capital.
Last activity — % of addresses vs. % of supply
Address age — % of addresses vs. % of supply
Timeline cohorts & recency
When today’s holders first appeared on-chain, and when addresses were last seen moving.
First appearance of current holders, by year
Addresses last active, by month (last 24 months)
Leaderboards top 500
Every address links to the explorer. Use the search box to filter by address or label.
Dataset raw CSV
The source data behind every chart and table on this page — free to download and reuse.
How it was made
- Exported from a fully synced
komododnode with address indexing enabled, by aggregating the complete on-chain transaction history of every KMD address up to block 4,970,673. - The full scan covers 3,052,657 addresses ever used on the chain. This extract keeps the 26,911 addresses holding at least 5 KMD at the snapshot — dust and emptied addresses are excluded, which is why “tracked supply” here is 142.81M KMD.
- Activity counters (
tx_count_30d / 90d / 365d) count transactions touching the address within the window ending at the snapshot date;tx_count_lifetimecovers the whole history. - Balances are the state at the snapshot block, not historical averages. One person can control many addresses, so address counts are an upper bound on holders.
- Labels come from known infrastructure lists (notary nodes, technical / pool addresses); anything unmatched is
unknown. Exchange, treasury, team and burn labels are reserved but not yet populated in this export.
Columns
| Column | Description |
|---|---|
address | KMD transparent address (R…) |
balance | Balance in KMD at the snapshot block |
balance_bucket | Band: <1, 1–10, 10–100, 100–1k, 1k–10k, 10k–100k, 100k+ |
first_tx_date | Date the address first appeared on-chain |
last_tx_date | Date of the most recent transaction |
tx_count_30d / 90d / 365d | Transactions in the trailing window before the snapshot |
tx_count_lifetime | All transactions ever involving the address |
label | exchange / treasury / team / notary / burn / technical / unknown |
Methodology
- Snapshot of the KMD UTXO set taken at block ().
- Per address: current balance, balance bucket, first / last transaction date, transaction counts over 30 / 90 / 365 days and lifetime, and a label (exchange, treasury, team, notary, burn, technical) where known.
- This extract covers addresses with a balance of at least KMD — dust addresses below the threshold are excluded, so “tracked supply” ( KMD) refers to this set.
- “Active” means at least one transaction inside the window; balances are as of the snapshot, not historical.