Disconnected from server
Markets
- Price, USD: -
- Price, KAS/BTC: -
- Market Cap: -
- Volume, 24h: -
CoinGecko
Data updates every ~30 seconds
Data updates every ~30 seconds
Network
- DAA Score: -
- Pruning Point: -
- Circulating Supply: -
- % CS Issued: -
- Mempool Entries: -
- Difficulty: -
- Hashrate: -
- Hashrate, 7d Change: -
- Hashrate, 30d Change: -
- Hashrate, 90d Change: -
Hashrate Chart | Difficulty Chart
Data updates every few seconds
u-Transactions Per Hour
The number of Unique Transactions per hour over the prior 24
hours.
This metric excludes Coinbase transactions.
The same transaction that appears in multiple blocks is counted as 1.
This metric excludes Coinbase transactions.
The same transaction that appears in multiple blocks is counted as 1.
Data updates every few seconds
Transaction Summary
Prior 24 Hours
Unique Transactions
- -Unique Count:The number of Unique Transactions over the prior 24 hours.
This metric excludes Coinbase transactions.
The same transaction that appears in multiple blocks is counted as 1. - -Unique TPS:The average Unique Transactions Per Second (TPS) over the last 24 hours.
This metric excludes Coinbase transactions.
The same transaction that appears in multiple blocks is counted as 1.
Output Script Classes
- -P2PK:The number of transaction outputs paying to a Schnorr public key (P2PK) over the prior 24 hours.
Counted per output, not per transaction. - -P2PK ECDSA:The number of transaction outputs paying to an ECDSA public key over the prior 24 hours.
Counted per output, not per transaction. - -P2SH:The number of transaction outputs paying to a script hash (P2SH) over the prior 24 hours. Covenant scripts are committed via P2SH.
Counted per output, not per transaction. - -Non-Standard:The number of transaction outputs with a non-standard script over the prior 24 hours.
Counted per output, not per transaction.
Non-standard outputs are rejected by node relay policy (mempool and gossip), so they can only reach the chain if a miner includes one directly in a block. They remain consensus-valid — standardness is a relay rule, not a consensus rule.
Data updates every few seconds
Transaction Inspection
Prior 24 Hours
Opcodes Activates Jun 30 Covenant & introspection metrics begin populating when the Toccata hardfork activates on Kaspa mainnet (June 30, 2026 · DAA score 474,165,565).
Activates Jun 30
Covenant & introspection metrics begin populating when the Toccata hardfork activates on Kaspa mainnet (June 30, 2026 · DAA score 474,165,565).
- -Introspection Opcode Transactions:The number of transactions using a covenant / introspection opcode over the prior 24 hours.
Detected by scanning a non-standard output script, or the redeem script revealed by a pay-to-script-hash spend, for an opcode in the covenant range (OpTxVersion–OpBlake3WithKey,0xb2–0xda). - -Introspection Opcode Outputs Spent:The number of pay-to-script-hash outputs spent over the prior 24 hours whose revealed redeem script uses a covenant / introspection opcode (
OpTxVersion–OpBlake3WithKey,0xb2–0xda).
A lower bound — only inputs whose spent output could be resolved are counted. - -ZK Precompile Transactions:The number of transactions using the ZK precompile opcode (
OpZkPrecompile) over the prior 24 hours.
Detected by scanning a non-standard output script, or the redeem script revealed by a pay-to-script-hash spend, for the ZK precompile opcode. - -ZK Precompile Outputs Spent:The number of pay-to-script-hash outputs spent over the prior 24 hours whose revealed redeem script uses the ZK precompile opcode.
A lower bound — only inputs whose spent output could be resolved are counted.
Covenants Activates Jun 30 Covenant & introspection metrics begin populating when the Toccata hardfork activates on Kaspa mainnet (June 30, 2026 · DAA score 474,165,565).
Activates Jun 30
Covenant & introspection metrics begin populating when the Toccata hardfork activates on Kaspa mainnet (June 30, 2026 · DAA score 474,165,565).
- -Covenant-Creating Transactions:The number of transactions that create at least one covenant-bound output over the prior 24 hours.
Covenant-id presence is a consensus binding on the output, independent of script opcodes. - -Covenant Outputs Created:The number of covenant-bound outputs created by accepted transactions over the prior 24 hours.
- -Covenant Outputs Spent:The number of covenant-bound outputs spent by accepted transactions over the prior 24 hours.
A lower bound — only inputs whose spent output could be resolved are counted.
Protocols
- -KRC Inscriptions:The number of known Kasplex KRC Inscriptions (KRC-20 and KRC-721) transactions over the prior 24 hours.
Reveal transactions are detected based on the presence of "kasplex" in signature script. The previous outpoint transaction of the given input is then counted as a commit transaction, if included in a block within the prior 24 hours.
All Reveal transactions are detected. While old Commit transactions may be missed due to the approach used. - -KNS:The number of known KNS transactions over the prior 24 hours.
Reveal transactions are detected based on the presence of "kns" in signature script. The previous outpoint transaction of the given input is then counted as a commit transaction, if included in a block within the prior 24 hours.
All Reveal transactions are detected. While old Commit transactions may be missed due to the approach used. - -Kasia:The number of known Kasia transactions over the prior 24 hours.
The presence of prefix "ciph_msg" in transaction payload is used to detect Kasia transactions. - -Kasplex L2:The number of known Kasplex L2 transactions over the prior 24 hours.
The presence of prefix "kasplex" at start of transaction payload is used to identify Kasplex L2 transactions. - -K Social:The number of known K Social transactions over the prior 24 hours.
The presence of prefix "k:" in transaction payload is used to detect K Social transactions. - -Igra L2:The number of known Igra L2 transactions over the prior 24 hours.
Payload matching Igra L1 payload is used to detect Igra L2 transactions.
Outputs Chart | Introspection Opcodes | ZK Opcodes | UTXO Count | Protocol Activity
Data updates every few seconds
Fees
Fee Rates
- -Low:An estimate for sub-hour DAG inclusion.
Estimated transaction fee = transaction mass * fee rate
See RpcFeeEstimate struct in rusty-kaspa codebase. - -Normal:An estimate for sub-minute DAG inclusion.
Estimated transaction fee = transaction mass * fee rate
See RpcFeeEstimate struct in rusty-kaspa codebase for more information. - -Priority:An estimate for sub-second DAG inclusion.
Estimated transaction fee = transaction mass * fee rate
See RpcFeeEstimate struct in rusty-kaspa codebase for more information.
Average Fee (in KAS)
- Prior 1 Minute: -
- Prior 1 Hour: -
- Prior 24 Hours: -
Total Fees (in KAS)
- Prior 1 Minute: -
- Prior 1 Hour: -
- Prior 24 Hours: -
Daily Total Fees Chart | Largest Fees Paid
Data updates every few seconds
Addresses By KAS Balance
Data updates every ~24 hours, around 00:00 UTC
Mining Share by Node Version
Last 36000 Blocks
Data updates every few seconds
Kaspalytics strives to provide accurate data - our highest level of effort is given to data
validation and maintenance. However, we cannot guarantee 100% accuracy. Data is subject to
inaccuracies and change.