Flow: User Activity, May 2nd

    Overview
    db_img

    On May 2nd, there was a massive spike in the number of active addresses on Flow which was multiple orders higher than the average daily count of users. This dashboard aims to uncover the source of this activity.

    Daily Activity
    Loading...
    Loading...

    The Flow blockchain is designed in a matter that three types of addresses are involved in each transaction:

    • Proposer: the address that proposes the transaction.
    • Payer: the address that pays for the transaction.
    • Authorizers: the addresses that authorize the transaction.

    The following charts depict the daily number of active addresses for each of the above types and also, the number of transactions recorded on the blockchain. As shown by the charts, there were multiple spikes over the past few months. This analysis was conducted based on the authorizer addresses since they are more inclusive compared to proposers and payers.

    Loading...
    Loading...
    Activity on May 2nd
    Loading...
    Loading...

    Limiting the activity to only May 2nd has demonstrated that more than 600k addresses were active on this day and registered 1.25 million transactions on the blockchain.

    Notable events during the first week of May

    Flow experienced a busy week over the first 7 days of May, including the release of multiple NFT collections, by both the new and well-known collections.

    While not all of these events happened on May 2nd, the current analysis took these events into account when conducting a deep dive into why the blockchain experienced massive user activity.

    Reference Tweets:

    db_img
    Limitations

    There were some cases in which the script of a transaction (on Flowscan) showed the interaction of an address with a particular contract address. However, since these data were not accessible, these types of transactions could not be categorized accurately.

    Sample Address: 0xda7e19fb686d8b3b

    Sample TX ID: f4c1496f72edc3b70b5f0c269449070e5d6cfa37177573e004ebf413e0012ab8

    The script for this sample transaction shows the interaction with the LNVCT contract.

    db_img