POST
/
2fc1de7f08c0465f6a28e3c355e0cb14
eth_sendRawTransactionSync
curl --request POST \
  --url https://base-mainnet.core.chainstack.com/2fc1de7f08c0465f6a28e3c355e0cb14 \
  --header 'Content-Type: application/json' \
  --data '{
  "jsonrpc": "2.0",
  "method": "eth_sendRawTransactionSync",
  "params": [
    "0xf86c808504a817c80082520894ab5db0e98b8ea6b7f9d8ad8e8ed0bc8fba0d1a2f870de0b6b3a764000080821b9f",
    "5000"
  ],
  "id": 1
}'
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "transactionHash": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
    "blockHash": "0xabcdefabcdefabcdefabcdefabcdefabcdefabcdefabcdefabcdefabcdefabcdefabcdef",
    "blockNumber": "0x12345",
    "gasUsed": "0x5208",
    "status": "0x1"
  }
}
Base API method eth_sendRawTransactionSync allows for the submission of a pre-signed transaction to the Base 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 you 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 wait time in milliseconds. If not provided, uses the node’s default timeout (typically 2 seconds). Must be a positive integer within the node-configured maximum timeout.

​
Response

  • result — the complete transaction receipt object containing transaction hash, block information, gas usage, contract address (if applicable), logs, and status.

​
Use case

The eth_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

Response

200 - application/json

Successful transaction submission with receipt

The response is of type object.