Fee reference
Quick-reference tables for SOL transaction costs
These tables summarise typical fee ranges for common instruction patterns. Figures are indicative and change with network conditions — always verify in an explorer before budgeting.
Last revised: August 2025. Printed copies at our Iffley Road room may carry an earlier revision date — check the footer of your sheet.
Base fee by transaction type
Base fee covers signature verification and a fixed per-signature charge. Most simple transfers use one signature.
| Transaction type | Typical signatures | Indicative base fee (SOL) | Notes |
|---|---|---|---|
| Simple SOL transfer | 1 | 0.000005 | Between two existing accounts |
| Transfer to new account | 1 | 0.000005 + rent | Rent-exempt minimum applies to new account |
| SPL token transfer | 1 | 0.000005 – 0.00001 | Depends on token program path |
| Token account creation | 1 | 0.000005 + rent | Associated token account |
| Simple swap (DEX) | 1 | 0.00001 – 0.00005 | Multiple inner instructions |
Priority fee guidance
Priority fees are optional micropayments to validators for faster inclusion during congestion. They are quoted in micro-lamports per compute unit.
| Congestion level | Suggested range (µ-lamports/CU) | When to consider |
|---|---|---|
| Low | 0 – 1,000 | Standard transfers, no urgency |
| Moderate | 1,000 – 10,000 | Time-sensitive payments, busy hours |
| High | 10,000 – 100,000+ | Competitive mints, volatile slots |
Total priority cost = (micro-lamports per CU × compute units consumed) ÷ 1,000,000, expressed in lamports then SOL.
Confirmation levels
- Processed — included in a block; may still be dropped in rare forks.
- Confirmed — supermajority of cluster voted on the block; suitable for most payments.
- Finalised — block rooted and unlikely to roll back; use for high-value settlements.
Using this reference in a session
These tables are a starting point for our workshops and drop-in hours. A tutor can walk you through how each row applies to your specific transactions using explorer data.