Sealevel

Definition: Sealevel is Solana’s parallel runtime for on-chain programs. It uses the accounts a transaction declares it will read or write to identify transactions that may be processed concurrently. Transactions that compete to write the same account can constrain that concurrency. Sealevel describes an execution and scheduling design; it is not a throughput guarantee or the name of the entire Solana network.12

Official terminologySolana Documentation
Architecture overviewSealevel — Parallel Processing Thousands of Smart Contracts
DirectoriesSolana Directory

In-Depth Explanation

Transactions declare the accounts they use

A Solana transaction identifies the accounts its instructions need and marks each account as readable or writable. That information is available to the validator before execution. Transactions that only read shared accounts, or that use separate writable accounts, can be scheduled concurrently when the validator has the resources to do so. This makes the execution path different from a design that must process every state change in one global sequence.1

Conflicting writes set limits

Parallel execution does not mean that all transactions run at once. If two transactions both need to change the same writable account, the validator has to respect the dependency between those operations. A busy application can concentrate activity on a small set of accounts, limiting how much work around those accounts can overlap. Transaction scheduling, program compute use, account locks, network conditions, and validator hardware all affect observed performance; the word “parallel” alone does not predict a user’s confirmation time or a network’s throughput.

Programs and account state

Solana programs contain executable code but are stateless. They read and update separate data accounts passed into each instruction, and account ownership rules determine which program can change an account’s data or debit its lamports. Sealevel can use the declared account access to schedule work, while the Solana Virtual Machine (SVM) and validator runtime execute programs under their instruction, account, and compute rules.23

Sealevel, the SVM, and Proof of History

These names refer to related but distinct parts of Solana’s design. Sealevel is the parallel runtime concept; the SVM is the program-execution environment; Proof of History (PoH) provides a cryptographic clock used in Solana’s ordering and consensus design. They work in the same network stack, but none of them alone provides the entire validator, consensus, or application system.2

What Sealevel does not guarantee

Sealevel does not eliminate account contention, compute limits, transaction fees, failed instructions, software bugs, or validator hardware constraints. A benchmark result depends on its workload, validator setup, transaction mix, and measurement method. Treat historical throughput claims as measurements from a particular test or period, not as a permanent capacity promise.

History

  • September 8, 2019: Solana published a technical overview describing Sealevel as a parallel runtime and explaining how transactions declare the state they read and write.2
  • March 16, 2020: Solana Mainnet Beta launched. The Solana Foundation’s May 2020 newsletter describes the launch and the work then underway to enable smart contracts on the cluster.4

Page updated: November 15, 2026.

Related Terms

Related Articles

See Also

Sources

  1. Solana. “Terminology.” Solana Documentation. Accessed November 15, 2026. https://solana.com/docs/references/terminology.
  2. Solana Foundation. “Sealevel—Parallel Processing Thousands of Smart Contracts.” September 8, 2019. https://solana.com/news/sealevel—parallel-processing-thousands-of-smart-contracts.
  3. Solana. “Programs.” Solana Documentation. Accessed November 15, 2026. https://solana.com/docs/core/programs.
  4. Solana Foundation. “May Newsletter.” June 24, 2020. Solana Media. https://solana.com/news/may-newsletter.