iota_executeTransactionBlock
Execute the transaction and wait for results if desired.BCS serialized transaction data bytes without its type tag, as base-64 encoded string
A list of signatures (
flag || signature || pubkey bytes, as base-64 encoded string). Signature is committed to the intent message of the transaction dataOptions for specifying the content to be returned
The request type, derived from
IotaTransactionBlockResponseOptions if NoneOptions:WaitForEffectsCert- Waits for TransactionEffectsCert and then returns to client. This mode is a proxy for transaction finality.WaitForLocalExecution- Waits for TransactionEffectsCert and ensures the node executed the transaction locally before returning. If the node fails to execute locally in a timely manner, a bool in the response indicates this.
The transaction digest
The transaction data
The effects of executing the transaction
Whether the transaction was executed locally on this node
cURL
iota_view
Calls a Move view function with the given package object ID, module, and function names.The fully qualified function name in the format
<package_id>::<module_name>::<function_name>Example: 0x3::iota_system::get_total_iota_supplyType arguments for the Move function call
Arguments to pass to the Move function
The return values from the view function as BCS-encoded bytes
cURL
Example: Query Object Type
cURL
iota_devInspectTransactionBlock
Runs the transaction in dev-inspect mode, which allows for nearly any transaction (or Move call) with any arguments. Detailed results are provided, including both the transaction effects and any return values.The address to use as the sender for the dev-inspect transaction
BCS encoded TransactionKind (as opposed to TransactionData, which includes gasBudget and gasPrice)
Gas is not charged, but gas usage is still calculated. Defaults to the reference gas price if not provided
The epoch to perform the call. Will be set from the system state object if not provided
Additional arguments including gas_budget, gas_objects, gas_sponsor and skip_checks
The effects of executing the transaction
Events emitted during execution
Results from the dev-inspect, including return values
Error message if the transaction failed
cURL
iota_dryRunTransactionBlock
Return transaction execution effects including the gas cost summary, while the effects are not committed to the chain.BCS serialized transaction data bytes, as base-64 encoded string
The effects of executing the transaction
Events emitted during execution
Changes to objects resulting from the transaction
Changes to balances resulting from the transaction
The input transaction data
cURL
Transaction Building Workflow
Typically, executing a transaction involves these steps:- Build Transaction - Construct the transaction using SDK methods or transaction builder APIs
- Dry Run (Optional) - Use
iota_dryRunTransactionBlockto preview effects and gas costs - Dev Inspect (Optional) - Use
iota_devInspectTransactionBlockfor detailed debugging - Sign Transaction - Sign the transaction bytes with your private key
- Execute Transaction - Submit via
iota_executeTransactionBlock
Gas Configuration
All transactions require gas configuration:- Gas Budget - Maximum IOTA to spend on gas (in NANOS)
- Gas Price - Price per unit of gas (use reference gas price or higher)
- Gas Objects - IOTA coin objects to use for paying gas
iotax_getReferenceGasPrice method.