Network activity. Made transparent

VIEW NODE UPTIME AND NETWORK STATUS

Transaction volume by network service

Understand Hedera network services usage on a per-second basis.

Time to consensus finality

See how efficiently hashgraph is functioning to deliver low-latency transaction finality.

Total number of accounts created

Research the rate at which accounts on the network are growing.

  • Month

  • Week

  • Day

  • Hour

- TPS by Service: average transaction speed over the last month is calculated as the number of transactions by 4 hour intervals divided by 14,400 seconds and broken down by service type

- Chart displaying zero TPS is due to missing data

- TPS by Service: average transaction speed over the last week is calculated as the number of transactions by 4 hour intervals divided by 14,400 seconds and broken down by service type

- Chart displaying zero TPS is due to missing data

- TPS by Service: average transaction speed over the last day is calculated as the number of transactions by 4 hour intervals divided by 14,400 seconds and broken down by service type

- Chart displaying zero TPS is due to missing data

- TPS by Service: average transaction speed over the last hour is calculated as the number of transactions by 4 hour intervals divided by 14,400 seconds and broken down by service type

- Chart displaying zero TPS is due to missing data

  • Month

  • Week

  • Day

  • Hour

- Consensus latency: measured as the difference (in seconds) between the time a node receives a transaction and the consensus timestamp assigned by the network

- Chart displaying zero seconds is due to missing data

- Consensus latency: measured as the difference (in seconds) between the time a node receives a transaction and the consensus timestamp assigned by the network

- Chart displaying zero seconds is due to missing data

- Consensus latency: measured as the difference (in seconds) between the time a node receives a transaction and the consensus timestamp assigned by the network

- Chart displaying zero seconds is due to missing data

- Consensus latency: measured as the difference (in seconds) between the time a node receives a transaction and the consensus timestamp assigned by the network

- Chart displaying zero seconds is due to missing data