eth_sendRawTransactionSync
Executing transactions | Arbitrum
eth_sendRawTransactionSync | Arbitrum
Arbitrum API method that submits a signed transaction and blocks until the transaction receipt is returned or the timeout expires.
POST
eth_sendRawTransactionSync
Arbitrum API method
eth_sendRawTransactionSync allows for the submission of a pre-signed transaction to the Arbitrum network and waits synchronously for the transaction receipt or a configurable timeout. This method reduces transaction submission latency by combining transaction submission and receipt retrieval into a single RPC call, based on EIP-7966.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
Parameters
signedTransactionData— the signed transaction data in hexadecimal format. This data includes the transaction details such as nonce, gas price, gas limit, to address, value, data, and the signature.timeout(optional) — maximum time to wait for the transaction receipt, in milliseconds, passed as a0x-prefixed hex-encoded quantity, for example0x1388for 5000 ms. If omitted, the node’s default applies (20 seconds in the standard Nitro configuration). Requests above the node’s maximum (60 seconds by default) are silently capped to the maximum rather than rejected.
Although EIP-7966 defines
timeout as a plain integer, Arbitrum Nitro—a go-ethereum fork—types it as a hex-encoded quantity (hexutil.Uint64), so you must pass it as a 0x-prefixed hex string. Plain integers (5000) and non-hex strings ("5000") are rejected with an invalid argument 1 error.Response
result— the complete transaction receipt object, the same structure returned by eth_getTransactionReceipt: transaction hash, block information, gas usage, contract address (if applicable), logs, and status. If the timeout elapses before the transaction is mined, the call returns an error instead of a receipt.
gasUsedForL1— the amount of gas spent on parent chain (L1) calldata, in units of child chain gas.l1BlockNumber— the block number of the first non-Arbitrum ancestor chain, usable forblock.numbercalls.timeboosted—trueif the transaction was sequenced through the Arbitrum Timeboost express lane,falseotherwise.
Use case
Theeth_sendRawTransactionSync method is particularly useful for:
- High-frequency applications requiring immediate transaction confirmation feedback.
- Layer 2 solutions with fast block times where rapid transaction throughput is critical.
- DApps and wallets seeking to improve user experience with faster transaction confirmations.
- Trading applications where transaction latency directly impacts performance.
- Applications requiring stronger delivery guarantees than standard asynchronous transaction submission.
Body
application/json
Last modified on June 16, 2026