Sei: Transaction executor

Execute Sei EVM transaction

Overview

This node executes transactions on the Sei EVM blockchain. It supports two modes of operation:

Use Transaction Builder Data: Executes a transaction using data prepared by a preceding Transaction Builder node.
Manual Parameters: Allows manual specification of all transaction parameters such as recipient, value, nonce, calldata, and gas limit.

Typical use cases include automating token transfers, contract interactions, or any custom transaction on the Sei EVM network. For example, you can build a transaction in one node and then execute it here, or directly specify transaction details to send tokens or call smart contract functions.

Properties

Name	Meaning
Execution Mode	How to get transaction data: - Use Transaction Builder Data: Execute using data from a connected Transaction Builder node. - Manual Parameters: Specify transaction parameters manually.
Blockchain	Target Sei EVM network: - Sei Mainnet EVM (Pacific-1) - Sei Testnet EVM (Atlantic-2) - Custom (requires specifying a custom RPC URL)
Custom RPC	Custom Sei EVM RPC endpoint URL. Required if "Custom" blockchain is selected.
Recipient Address	The recipient address in hexadecimal format (0x...). This is the destination of the transaction.
Value	Amount of SEI tokens to send with the transaction, specified as a number with up to 8 decimal places.
Nonce	Transaction nonce, an integer representing the transaction count for the sender's account.
Calldata	Hexadecimal string representing the transaction calldata (e.g., encoded function call and parameters).
Gas Limit	Gas limit for the transaction, specifying the maximum amount of gas units that can be consumed.

Output

The node outputs an array with one item per input item, each containing a JSON object with the following structure:

success (boolean): Indicates whether the transaction was successfully sent and confirmed.
transactionHash (string): The hash of the submitted transaction.
receipt (object): The transaction receipt returned after confirmation, including status, gas used, logs, etc.
txData (object): The transaction data used for sending, including fields like to, nonce, gasLimit, data, and value.
rpcUrl (string): The RPC endpoint URL used to send the transaction.
timestamp (string): ISO timestamp when the transaction was executed.

If an error occurs, the output JSON includes:

success: false
error: true
errorMessage: Description of the error encountered.
timestamp: ISO timestamp of the failure.

The node does not output binary data.

Dependencies

Requires an API key credential for accessing the Sei EVM network.
Uses the ethers library for Ethereum-compatible transaction creation and signing.
Needs access to a valid RPC endpoint URL for the target Sei EVM network; default endpoints are provided but may be rate-limited.
If using a custom network, a custom RPC URL must be supplied.

Troubleshooting

No transaction data found: When using "Use Transaction Builder Data" mode, ensure the previous node provides valid transaction data (txData) and an RPC URL.
No RPC URL found: The transaction data must include a valid RPC URL; otherwise, the node cannot connect to the blockchain.
Custom RPC URL required: If selecting a custom blockchain, you must provide a valid RPC URL.
Unknown network: Selecting a blockchain option not recognized by the node will cause an error.
Invalid recipient address or calldata: Ensure addresses are in correct hex format and calldata is properly encoded.
Nonce issues: The node fetches the nonce automatically if missing, but manual nonce must be accurate to avoid transaction replacement or rejection.
Gas limit too low: Transactions may fail if the gas limit is insufficient.
API key or RPC connectivity problems: Verify credentials and network availability.