In both Solana and Fuel, the account lists provide coarse-grained concurrency control at the account level meaning that only transactions accessing different accounts can be processed in parallel without conflicts. Transactions that access the same account, even if they access different states within that account, are subject to serial execution to prevent potential conflicts and ensure state consistency.

However, both Solana and Fuel’s concurrency control mechanisms do not support intra-contract parallelization, meaning that transactions calling the same contract must be processed sequentially to ensure data consistency and prevent conflicts.

It is a common pattern that when a popular decentralized application (dApp) is released, a large portion of the transactions on the blockchain are related to that application. It can attract a significant number of users and generate a high volume of transactions. It is obvious that a blockchain must be capable of parallelizing concurrent calls to the same smart contract

Last updated