The price per compute unit in micro-lamports that a transaction is willing to pay as a priority fee. Set via the Compute Budget Program's SetComputeUnitPrice instruction. Higher prices increase the likelihood of a transaction being included by the leader during congestion. The effective priority fee equals the compute unit price multiplied by the compute units consumed, converted from micro-lamports to lamports.
Start with the shortest useful explanation before going deeper.
The price per compute unit in micro-lamports that a transaction is willing to pay as a priority fee. Set via the Compute Budget Program's SetComputeUnitPrice instruction. Higher prices increase the likelihood of a transaction being included by the leader during congestion. The effective priority fee equals the compute unit price multiplied by the compute units consumed, converted from micro-lamports to lamports.
Use the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.
Think of it as one of the core moving pieces your program reads, writes, or invokes at runtime.
Place the term inside its Solana layer so the definition is easier to reason about.
Accounts, instructions, PDAs, transactions, and execution flow.
Turn the term from vocabulary into something operational for product and engineering work.
This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.
Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.
Compute Unit Price (compute-unit-price) Category: Programming Model Definition: The price per compute unit in micro-lamports that a transaction is willing to pay as a priority fee. Set via the Compute Budget Program's SetComputeUnitPrice instruction. Higher prices increase the likelihood of a transaction being included by the leader during congestion. The effective priority fee equals the compute unit price multiplied by the compute units consumed, converted from micro-lamports to lamports. Related: Micro-Lamport, Compute Units (CU), Priority Fee
Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.
Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.
The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.
These branches show which concepts this term touches directly and what sits one layer beyond them.
The unit used to express compute unit pricing for priority fees on Solana. One lamport equals 1,000,000 micro-lamports. When setting a compute unit price via the Compute Budget Program, the price is specified in micro-lamports per compute unit. The total priority fee is calculated as (compute unit price in micro-lamports * compute units consumed) / 1,000,000, rounded down to lamports.
A measure of computational resources consumed by transaction execution, analogous to gas on Ethereum. Each BPF instruction costs CU; syscalls have predefined CU costs (e.g., SHA-256: 85 CU base + per-byte). Default per-instruction limit is 200,000 CU; max per-transaction is 1,400,000 CU. Priority fee cost = CU price × CU consumed.
An optional additional fee paid on top of the base fee to increase the likelihood that a transaction is processed quickly by the current leader, expressed as a price in micro-lamports per compute unit (CU). The total priority fee equals (compute unit price × compute unit limit) / 1,000,000 lamports. Leaders sort transactions in their queue by fee-per-CU, so setting a competitive priority fee is the primary mechanism for ensuring reliable transaction landing during congestion.
These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.
These entries are easy to mix up when you are reading quickly, prompting an LLM, or onboarding into a new layer of Solana.
The maximum compute units a transaction can consume. Default is 200,000 CU per instruction (max 1.4M CU per transaction). Programs can request specific limits via the ComputeBudgetProgram's SetComputeUnitLimit instruction. Under-requesting CU risks transaction failure; over-requesting wastes priority fee budget.
A native Solana program (address: ComputeBudget111111111111111111111111111111) that allows transactions to configure their compute resource limits. It provides two key instructions: SetComputeUnitLimit (set the max CU a transaction can consume, up to 1.4M) and SetComputeUnitPrice (set the micro-lamport price per CU for priority fees). These instructions must appear before any program instructions in the transaction.
A measure of computational resources consumed by transaction execution, analogous to gas on Ethereum. Each BPF instruction costs CU; syscalls have predefined CU costs (e.g., SHA-256: 85 CU base + per-byte). Default per-instruction limit is 200,000 CU; max per-transaction is 1,400,000 CU. Priority fee cost = CU price × CU consumed.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
The unit used to express compute unit pricing for priority fees on Solana. One lamport equals 1,000,000 micro-lamports. When setting a compute unit price via the Compute Budget Program, the price is specified in micro-lamports per compute unit. The total priority fee is calculated as (compute unit price in micro-lamports * compute units consumed) / 1,000,000, rounded down to lamports.
A measure of computational resources consumed by transaction execution, analogous to gas on Ethereum. Each BPF instruction costs CU; syscalls have predefined CU costs (e.g., SHA-256: 85 CU base + per-byte). Default per-instruction limit is 200,000 CU; max per-transaction is 1,400,000 CU. Priority fee cost = CU price × CU consumed.
An optional additional fee paid on top of the base fee to increase the likelihood that a transaction is processed quickly by the current leader, expressed as a price in micro-lamports per compute unit (CU). The total priority fee equals (compute unit price × compute unit limit) / 1,000,000 lamports. Leaders sort transactions in their queue by fee-per-CU, so setting a competitive priority fee is the primary mechanism for ensuring reliable transaction landing during congestion.
These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.
The fundamental data storage unit on Solana. Every piece of state is stored in an account identified by a 32-byte public key. Accounts hold a lamport balance, an owner program, a data byte array (up to 10MB), and an executable flag. Only the owning program can modify an account's data, but anyone can credit lamports to it.
Executable code deployed on-chain, equivalent to a smart contract on other blockchains. Programs are stateless—they store no data themselves but read/write data in separate accounts they own. Programs are compiled to SBF bytecode and loaded via the BPF Loader. Every program has a unique Program ID (its account's public key).
A single operation within a transaction that invokes a program. An instruction specifies: (1) the program ID to call, (2) an array of account metas (pubkey, is_signer, is_writable), and (3) an opaque data byte array. Programs decode the instruction data to determine which operation to perform.
An atomic unit of execution containing one or more instructions, a recent blockhash, and one or more signatures. All instructions in a transaction execute sequentially and atomically—if any instruction fails, the entire transaction reverts. Transactions have a 1,232-byte size limit (matching IPv6 MTU) and a default 200,000 CU budget.