Simulate multiple Solana transactions in a single request to get balance changes, state updates, and risk analysis for each.
payload and encoding_type
parameters as the
single transaction endpoint.
Cluster support: devnet, testnet, mainnet-beta
| Field | Description |
|---|---|
instruction_groups | Hierarchical view of all instructions with parsed data. |
asset_transfers | Detected SOL and token transfers. |
lamport_changes | Balance changes by address. |
expected_state_changes | Predicted account-level state updates. |
transaction_risk | Risk analysis with accounts_risk_score and exploit_risks_detected. |
returned_data | Data returned by programs during execution. |
logs | Complete execution logs. |
transaction_summary | Compute units, fee breakdown, programs invoked. |
error | Failure reason if simulation failed for this transaction. |
Use Authorization: Bearer
Successful batch simulation response. Returns an array of simulation results, each containing transaction execution details, state changes, and risk analysis.
Structured view of all transaction instructions, organized hierarchically with outer instructions and their corresponding inner instructions. Each instruction contains programId, program name (when parsed), parsed instruction data, raw data, accounts, and nesting level.
Detected asset movements during transaction execution. Includes source, destination, mint, and amount. Shows both SOL transfers and token transfers.
List of lamport balance changes by address, showing pre and post-execution balances.
Predicted account-level state updates based on simulation. Includes formatted details like assets, human-readable descriptions of changes, and metadata for UI rendering.
Comprehensive risk analysis containing accounts_risk_score and exploit_risks_detected. Includes individual risk scores for each address, proximity to known malicious addresses, and summary statistics.
Any data returned by programs during execution.
Complete transaction execution logs from the Solana runtime.
Concise overview including compute units consumed, fee breakdown (compute fee, prioritization fee, tips), programs invoked with their instruction types, and transaction version.
Indicates if the transaction simulation failed, containing the reason for failure (e.g., AccountNotFound, InsufficientFunds, etc.). If present, other fields may be incomplete as execution terminated early.