Contracts Deployed

    Provide an updated view of contracts deployed over time on NEAR.

    Loading...

    In this dashboard, we want to review and analyze the smart contracts deployed on the Near blockchain:

    For this dashboard, we have used two tables of “actions_events“ and “transactions“.

    At first, using the “actions_events“ table, we have found the transactions related to the smart contract deployment. And then we have found these transactions in the “transactions“ table.

    And in the following, we have extracted the case information from the “transactions“ table.

    According to the charts and explanations above, it can be understood that despite the downward trend of the market and the reduction of new deployed contracts, developers and users are still active. And also the growing process and development of contracts is as good as in the past.

    Loading...
    Loading...

    In the chart on the right, you can see the top 10 smart contracts that have been developed and updated the most:

    As you can see, the first contract has been updated more than 400 times.

    In the chart below, you can also see the amount of deployment and updating of Near blockchain smart contracts on a weekly basis:

    As you can see, there is no noticeable decrease compared to a few months ago, which means that the development process is still going on.

    Loading...
    Loading...

    On the right, you can see the total number of smart contracts deployed so far:

    So far, more than 16,000 smart contracts have been created on the Near blockchain, and this is a relatively acceptable statistic.

    In the chart below, you can also see the number of deployed smart contracts on a weekly basis:

    In the “transactions“ table, for each contract, there is the possibility of multiple deployment transactions, so to access the smart contract creation time, we must obtain the minimum time for each contract.

    Loading...

    In the graph on the left, you can see the top 10 contracts with the most interaction:

    As can be seen, the most interaction of users with smart contracts is related to two smart contracts in Near blockchain. And these two contracts have been able to acquire a large volume of users and transactions.

    In the chart below, you can also see the amount of user interaction with Near blockchain smart contracts on a weekly basis:

    Loading...
    Loading...
    Loading...
    Loading...

    In the chart below, you can see the number of active developers on the Near blockchain on a weekly basis:

    As can be seen from the graph below, the number of active developers in the blockchain has not decreased much, unlike the above trend. And this means that despite the bearish market, developers are still active and optimistic about Near blockchain and its future.

    As can be understood from the above diagram, the level of user interaction with smart contracts deployed on Near blockchain has not changed much compared to the past, and users are still interacting with smart contracts as before.

    As it is clear from the graph above, in recent weeks, the number of new smart contracts deployed has decreased significantly compared to several months ago. And this can be due to the market conditions and its bearishness.

    In the chart below, you can also see the deployment process of smart contracts on a monthly basis: As it is clear from this graph, during the last few months, as the market went down, the number of new contract deployments also decreased.

    In the chart below, you can also see the number of new developers who started working on the Near blockchain every week:

    This chart is also promising like the chart above, and shows that despite the bearish market, new developers are still being added to the Near blockchain as in the past. And that is very good.

    In the chart below, you can also see the level of activity and interaction of Uniqe users with the contracts deployed in the Near blockchain:

    And this diagram, like the diagram above, shows that users are active as before.

    db_img