method
how kaspa pulse gets each number on the home page.
- counted means we count it ourselves
- source names who we read it from
- computed means we work it out from fixed protocol rules
number of the week
source kraken, average computedhow far kaspa's weekly close sits above or below the plain average of its last 50 weekly closes. a week closes on saturday at 24:00 utc.
source kraken daily candles, the average computed by kaspa pulse
blocks per second
countedhow many blocks the network adds each second, read as the rise of the virtual DAA score over 600 seconds.
counted by kaspa pulse from the kaspa rest api
fees in miner revenue
source kaspalyticsthe share of transaction fees in everything miners earned over 30 days, fees divided by fees plus new coins.
fees source kaspalytics, new coins computed by kaspa pulse from the emission schedule
daily emission
computedthe new KAS created per day, the block reward times 10 blocks a second times 86,400 seconds. the reward steps down every month by the same factor and halves once a year.
computed by kaspa pulse from the emission schedule
addresses with at least 100 KAS
source kaspalyticshow many addresses hold 100 KAS or more at the end of a day. an address is not a holder, one wallet can use many addresses.
source kaspalytics address thresholds
addresses with any balance
source kaspalyticsevery address with a balance above zero, next to those holding more than 0.01 KAS. most of the first group hold dust.
source kaspalytics address thresholds
the monday reading
every number on the home page and on each week page is the reading of a monday. a value measured after that monday is not shown on its week page, so a week can show fewer numbers than the next.
the comparison chips
fast numbers are compared with the week before and with 13 weeks before, the emission with the month before and with 3 months before. fixed numbers get no comparison. when a value is missing, its chip is left out.