With the recent Crescendo Upgrade on Flow, which integrates Ethereum Virtual Machine (EVM) support, several key metrics related to block performance need to be closely monitored to assess the network's performance as it adapts to this change. Here's a breakdown of the important metrics we will focus on:

1. Block Time (Seconds Between Blocks)

- Pre-Upgrade: Block time on Flow has traditionally been optimized for native transactions, with relatively fast and consistent block production.

- Post-Upgrade: EVM transactions introduce new factors that could impact block time. As the network adapts to handling EVM-based smart contracts and transactions, we might see some variations in block time, but this metric will help us track whether the network can maintain its efficiency as EVM activity grows.

2. Transactions per Block

- Pre-Upgrade: Flow has maintained a steady transaction count per block, largely driven by its native transaction system, including NFTs and smart contracts.

- Post-Upgrade: With EVM support, we anticipate an increase in transaction density per block. As more projects deploy Ethereum-based smart contracts on Flow, this metric will help us monitor how the network handles the additional load and whether the transaction capacity per block increases significantly.

3. Total Number of Blocks

- Pre-Upgrade: The number of blocks produced is determined by Flow's native transaction cadence.

- Post-Upgrade: Following the integration of EVM, we expect to see potential changes in the total number of blocks produced, especially as EVM activity grows. Tracking the number of blocks will provide insights into the network's capacity to scale and handle both native and EVM-based transactions.

4. Network Throughput and Scalability

- Pre-Upgrade: Flow has demonstrated high throughput and scalability, processing a large volume of transactions efficiently.

- Post-Upgrade: As the upgrade unfolds, it’s important to monitor whether Flow’s network continues to scale effectively with the added complexity of EVM transactions. This metric will provide an understanding of Flow’s ability to maintain high throughput while handling new types of transactions introduced by the EVM.

These metrics will give us a clear view of how the Crescendo Upgrade is impacting Flow’s block performance, enabling a detailed comparison between EVM and non-EVM activity.

1. Number of Blocks: Post-upgrade, the number of blocks produced has notably increased, doubling compared to the period before the upgrade. This surge reflects the network's capacity to handle a higher volume of transactions and demonstrates its improved scalability with the integration of EVM.

2. Transactions per Block: Despite the substantial increase in the number of blocks, the average number of transactions per block has remained relatively stable. This stability suggests that while the network is processing more blocks, the transaction density per block has not significantly changed, indicating a consistent transaction load distribution.

3. Average Time Between Blocks: Initially, the time between blocks for EVM transactions was higher than that for native transactions, indicating potential delays or inefficiencies in processing. However, this metric has since improved, with the average time between blocks for EVM transactions now being lower than before the upgrade. This improvement suggests that the network has successfully optimized its performance and reduced latency for EVM-based transactions.

Overall, the Crescendo Upgrade has led to a more efficient and scalable network, with an increased number of blocks and improved block time performance for EVM transactions. While the average number of transactions per block has remained consistent, the reduced latency and higher block throughput underscore the positive impact of the integration on Flow's blockchain performance.