Kasplex EVM
Follow indexed transaction activity, accounts, contracts and token metrics from the Kasplex EVM environment.
Explore →KASPA ECOSYSTEM
Kaspa ecosystem activity, organized by layer.
The Kaspa ecosystem now spans the base network, token standards, EVM environments and DeFi applications. KAS Watch keeps those layers separate so activity on Kasplex, KRC-20 or a DeFi protocol is not presented as if it were the same thing as Kaspa L1 activity.
KRC-20
Review indexed KRC-20 token counts and recent deployment or minting context from the configured indexer.
Explore →DeFi context
Track selected Igra and ecosystem metrics while keeping protocol activity distinct from base-layer network measurements.
Explore →Separating Kaspa L1, KRC-20, Kasplex EVM and DeFi activity
The Kaspa ecosystem includes several kinds of activity that should not be merged into one number. Base-layer network metrics describe Kaspa L1. KRC-20 activity depends on token-indexer data. Kasplex EVM metrics come from an EVM environment and its explorer or indexer. DeFi metrics may come from individual protocols or ecosystem APIs.
KAS Watch keeps those layers visibly separate. That means a rise in EVM transactions is presented as EVM activity, not as if it were the same measurement as Kaspa L1 transactions. Likewise, KRC-20 deployment or minting data is labeled as token-indexer activity rather than base-layer consensus data.
This source-aware structure matters because different APIs have different definitions, update schedules and availability. The ecosystem workspace is intended to show where activity is happening and how it is changing while preserving the boundary between each layer and data source.
Last reviewed: October 7, 2026 · KAS Watch separates observed data from interpretation.
Common questions
What does KAS Watch track in the Kaspa ecosystem?
KAS Watch tracks selected Kasplex EVM, KRC-20 and DeFi metrics alongside separate Kaspa L1 network analytics.
Are Kasplex EVM transactions the same as Kaspa L1 transactions?
No. They are different activity layers and KAS Watch keeps their metrics separate.
Why can ecosystem metrics differ between websites?
Different explorers and indexers can use different definitions, update schedules and data pipelines, so KAS Watch labels the source and layer for context.
Methodology matters
Ecosystem metrics depend on the availability and definitions of their underlying indexers and APIs. KAS Watch labels the layer and source so an EVM, token-indexer or DeFi metric is not confused with Kaspa base-layer consensus data.