Try Quests to earn FLOWPolygon Block Performance
Outline
In this report, we are taking a look at the Polygon’s block performance. We analyze the total number of blocks created in the Polygon network so far, the average time between two consecutive blocks, the min and max time it took the network to create blocks and the average transactions per block. We then compare these statistics with two L1 and L2 networks, namely, Flow and Arbitrum.
Notes:
- This dashboard updates on a daily basis.
- This report has been created on July 26, 2022.
Basic Statistics of Polygon Blocks
The statistics on the left shows the 5 important metrics on for Polygon’s block performance.
Our observations:
- In total, 1.92 Million blocks have been creating so far in the Polygon network.
- On average, it there is a 2,250 gap between the creation time of polygon blocks.
- The minimum gap between two Polygon blocks were 2,000 Millisecond, which is close to the average time. This means that Polygon blocks are being creating close to min time or very fast.
- The maximum time ever occurred between two blocks are 25,000 Milliseconds or 25 Seconds.
- On average, each block in Polygon network registered 75 transactions.
Polygon vs. Flow
Now lets compare Polygon block performance with Flow network’s.
Our observations:
- While Polygon has close to 2 Million blocks, Flow has 5.79 Million, almost 3 times the Polygon’s.
- On average Flow’s blocks are created every 1458 Milliseconds, which means Flow is faster than Polygon when comes to generating blocks.
- The minimum time between to Flow blocks were 0 Milliseconds, while Polygon never experienced a below 2 Seconds gap. This can mean there is a threshold for block generation gap.
- The maximum time between two Flow blocks were 17.1 Million Milliseconds or 4.75 hours. While Polygon never had more than 25 Seconds between blocks, for Flow, it can mean there was an outage during that time.
- The average number of blocks for Flow is almost 1/5 of the Polygon’s. This metrics along with the low average time between the blocks can suffice the high number of blocks in Flow network.
Polygon vs. Arbitrum
Finally, lets compare Polygon to an L2 network, namely Arbitrum.
Our observations:
-
Same as Flow, the number of blocks on Arbitrum network is more than Polygons, about 50%.
-
The average time between blocks for Arbitrum is 1,106 Milliseconds, less than both Polygon and Flow. This meas that, on average, it takes less than a second for a new block to be generated on the Arbitrum network.
-
Both Flow and Arbitrum experience a 0 Milliseconds gap between two consecutive blocks, while Polygon’s was 2 Seconds.
-
The max gap between two Arbitrum blocks were 23.4 Million Milliseconds or 6.5 hours. Same as Flow, Arbitrum might have experienced an outage.
-
Arbitrum had the least number of transactions per blocks, about 1.164. This means on average there are less than 2 transactions per Arbitrum block, which might indicate the low tendency to use Arbitrum, specially after the outage after their Odyssey campaign.
\
Conclusions
In this report, we have analyzed the Polygon’s block performance. We have found that:
- Polygon is a relatively busy network, considering its 75 transactions per block on average.
- Though Polygon has a less number of blocks compared to Flow and Arbitrum, it has higher number of transactions per block and is more consistent considering the gap between consecutive blocks, given it min and max time between blocks.
- Though Flow and Arbitrum networks are fast in block creation, they highly inconsistent when it comes to the gap between consecutive blocks.
