Submit a trial contract invocation to simulate how it would be executed by the network. This endpoint calculates the effective transaction data, required authorizations, and minimal resource fee. It provides a way to test and analyze the potential outcomes of a transaction without actually submitting it to the network.
<xdr.TransactionEnvelope>- The transaction to be simulated (serialized in base64)
<string>- Stringified-number of the recommended minimum resource fee to add when submitting the transaction. This fee is to be added on top of the Stellar network fee.
<object>- Information about instructions used, etc.
<string>- Stringified-number of the total cpu instructions consumed by this transaction
<string>- Stringified-number of the total memory bytes allocated by this transaction
erroris present then results will not be in the response. There will be one result object for each Host Function invocation, in the same order the Host Function was supplied.
<xdr.ScVal>- (optional) Only present on success. xdr-encoded return value of the Host Function call.
<xdr.ContractAuth>- Per-address authorizations recorded when simulating this Host Function call. (an array of serialized base64 strings)
<xdr.SorobanTransactionData>- The recommended Soroban Transaction Data to use when submitting the simulated transaction. This data contains the refundable fee and resource usage information such as the ledger footprint and IO access data (serialized in a base64 string).
<xdr.DiagnosticEvent>- Array of the events emitted during the contract invocation(s). The events are ordered by their emission time. (an array of serialized base64 strings)
<string>- Stringified-number of the current latest ledger observed by the node when this response was generated.
<string>- (optional) only present if the transaction failed. This field will include more details from
stellar-coreabout why the invoke host function call failed.