Introduction

Polygon is a protocol stack that was developed with the intention of resolving Ethereum's scalability difficulties. The issues that plague the network are remedied by the Polygon network, which manages transactions on a different blockchain that is interoperable with Ethereum.

After the transactions have been processed, Polygon sends them back to the primary Ethereum network. This strategy reduces the amount of strain placed on Ethereum's network. Because of this, Polygon is able to expedite transactions while simultaneously reducing their cost to less than a cent.

NEAR is a blockchain platform for building highly scalable decentralized applications that supports smart contracts. Over a hundred thousand transactions per second are possible. The dApps can be deployed and run on the NEAR blockchain's community-managed cloud infrastructure. It's like a serverless database in that it takes the best features of both centralized and distributed databases. NEAR's token is what makes the platform work, and it also allows apps developed on the NEAR ecosystem to communicate with one another in various ways. These aspects of the NEAR blockchain let programmers to create censorship-resistant back-ends for smart contracts that deal with sensitive information such as personal details, assets, and finances. Basic components make up the NEAR platform. The platform's native coin is an example of one of these key pieces. \n \n Osmosis (OSMO) is an automated market-making protocol (AMM) that is constructed on its own blockchain using the Cosmos SDK and IBC technologies, with a focus on the Interchain DeFi movement. Osmosis is a high-level protocol with a special emphasis on adaptable multi-purpose modules (AMMs), allowing users to build and deploy AMMs that are both unique and highly customized through the usage of a wide range of available modules and an on-chain governance framework.

How to find data?

Basically all data related blocks from Polygon, NEAR and Osmosis are from tables blow:

• near.core.fact_blocks
• polygon.core.fact_blocks
• osmosis.core.fact_blocks
• arbitrum.core.fact_blocks

From data in tables above, we can answer the questions:

• What is the average time between blocks on Polygon?
• What was the maximum and minimum recorded time between two blocks?
• How many transactions are done in a block on average?
• How do these numbers compare to L1s and L2s blockchains?

In term of time between blocks, from the charts, we can see:

• Polygon has the highest minimum time between blocks with 2 seconds.
• Osmosis has the highest maximum time and average time between blocks with 393194 seconds and 6.54 seconds respectively.
• Both Arbitrum and Near has no minimum time between block with 0 second.

In term of transaction per block, from the charts, we can see:

• Polygon has the highest number of transactions in a block with 1332 transactions. It also has the highest number of average transaction per block with 74.8368 transactions
• All chains in the analysis have the minimum number of transaction per block is 0.
• Arbitrum has the lowest number of transaction per block with only 128 transaction. This chain also has the lowest number of average transaction per block with 1.16 transaction