Transaction Simulation
Solana Transaction Simulation
Simulate one or more Solana transactions.
POST
Request fields accept both
camelCase and snake_case. See Request Field Names.sol_transactions is one of two shapes: a serialized transaction (transaction + optional encoding), or a structured transaction (feePayer + instructions). Alias transactions is also accepted for the array.
This endpoint has no
approve_changes, ownership_changes, call_graph, balance_table, logs, revert, or revert_reason. Solana has no ERC-20 approvals or EVM-style internal calls as primitives. Per-transaction failure is reported in error (null on success).Native SOL balance changes use
token_address: "native".risk_level Scale
Used in involved_addresses_risks. Same scale as Transaction Simulation.
A failed simulation is still a successful API call. The envelope stays
code: "0", status: "ok". Read exec_summary.result_code and results[i].error. Only infrastructure failures produce non-"0" codes. compute_units_consumed is 0 on simulator failure.Headers
Your HashDit API key
Body
application/json
Solana transactions to simulate
Transactions to simulate. Minimum 1. Alias transactions also accepted. Each item is either a serialized transaction or a structured transaction.
Minimum array length:
1Serialized (transaction) or structured (feePayer + instructions).
- Serialized transaction
- Structured transaction