Skip to main content


Execute a transaction with a serialized signature

Execute a transaction with a serialized signature


Write API

Execute the transaction and wait for results if desired. Request types: 1. WaitForEffectsCert: waits for TransactionEffectsCert and then return to client. This mode is a proxy for transaction finality. 2. WaitForLocalExecution: waits for TransactionEffectsCert and make sure the node executed the transaction locally before returning the client. The local execution makes sure this node is aware of this transaction when client fires subsequent queries. However if the node fails to execute the transaction locally in a timely manner, a bool type in the response is set to false to indicated the case. request_type is default to be `WaitForEffectsCert` unless options.show_events or options.show_effects is true


  • tx_bytes : <Base64> - BCS serialized transaction data bytes without its type tag, as base-64 encoded string.
  • signature : <Base64> - `flag || signature || pubkey` bytes, as base-64 encoded string, signature is committed to the intent message of the transaction data, as base-64 encoded string.
  • options : <TransactionBlockResponseOptions> - options for specifying the content to be returned
  • request_type : <ExecuteTransactionRequestType> - The request type, derived from `SuiTransactionBlockResponseOptions` if None


SuiTransactionBlockResponse : <TransactionBlockResponse>

Example Request and Result for sui_executeTransactionBlock


--location --request POST '<project_id>' \
--header 'Content-Type: application/json' \
--data-raw '{
"jsonrpc": "2.0",
"id": 1,
"method": "sui_executeTransactionBlock",
"params": [