Solana Fee Calculator“Transaction too large” on Solana
The serialized transaction is longer than the 1,232 bytes a legacy or v0 transaction may have.
Transaction too large: 1300 > 1232
Cause
Signatures (64 bytes each), account keys (32 bytes each), the blockhash and instruction data all count. Swaps through several pools and transactions with many accounts reach the limit first.
Fix
- Use a v0 transaction with address lookup tables: an account in a table costs one byte instead of 32.
- Split the work into two transactions, or reduce instruction data.
- The transaction-size calculator shows where the bytes go.
Fee charged? No. A transaction that is too large cannot be sent at all.
FAQ
What does “Transaction too large: 1300 > 1232” mean?
Signatures (64 bytes each), account keys (32 bytes each), the blockhash and instruction data all count. Swaps through several pools and transactions with many accounts reach the limit first.
How do I fix it?
Use a v0 transaction with address lookup tables: an account in a table costs one byte instead of 32. Split the work into two transactions, or reduce instruction data. The transaction-size calculator shows where the bytes go.
Was I charged a fee?
No. A transaction that is too large cannot be sent at all.
“Insufficient funds for rent”“Exceeded CUs meter” / “Computational budget exceeded”“Blockhash not found” when sending a Solana transaction“Transaction simulation failed”