multichain
/index /tools /34 solana-compute-units
live

Compute
units.

Default
200k
CU per instruction
Cap
1.4M
CU per transaction
Tip unit
μlam
per compute unit
SOL
live price
/34CU BUDGET CALCULATOR
CU budget
compute units
priority rate
micro-lamports / CU
total fee
base 5,000 + tip

/reference — typical consumption

operationcompute unitsnote
SOL transfer ~150 – 500 System Program is nearly free
SPL token transfer ~4,500 – 6,000 token program checks + balance writes
Create token account (ATA) ~20,000 – 30,000 one-time per wallet per token
Simple AMM swap ~40,000 – 120,000 single pool, direct route
Aggregator swap (multi-hop) ~200,000 – 1,000,000 route dependent, simulate first
NFT mint (Metaplex) ~100,000 – 300,000 metadata + master edition writes
Default budget 200,000 / instruction applied when you set no limit
Hard cap 1,400,000 / transaction consensus limit

/faq

01

What is a compute unit?

Solana's meter for execution work, the same role gas units play on Ethereum. Every instruction consumes CU as it runs; a transaction declares a budget and is killed if it exceeds it. Blocks also cap total CU, so budgets are the resource validators actually schedule.

02

Do I pay for the budget or for actual usage?

The priority fee is charged on your requested budget, not measured usage, which is the economic nudge to set accurate limits. Requesting the default 200,000 CU for a 5,000 CU token transfer pays 40 times more tip than needed.

03

How do I find my transaction's real CU usage?

Simulate it: simulateTransaction returns unitsConsumed, and explorers show CU for confirmed transactions. Set your limit slightly above the measured figure with a safety margin for state-dependent branches.

04

Why is the fee so small even with a tip?

Rates are in micro-lamports, millionths of a lamport, which is itself a billionth of a SOL. A generous 50,000 micro-lamport rate on a 200,000 CU budget is 10,000 lamports: a hundredth of a cent at most SOL prices.