> For the complete documentation index, see [llms.txt](https://docs.validationcloud.io/v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.validationcloud.io/v1/monad/execution-api/eth_sendrawtransactionsync.md).

# eth\_sendRawTransactionSync

Submits a signed transaction and synchronously waits for it to be included in a block, returning the full transaction receipt. Unlike [`eth_sendRawTransaction`](/v1/monad/execution-api/eth_sendrawtransaction.md), which returns only the transaction hash immediately, this method blocks until the transaction is executed and returns the complete receipt in a single call.

This is a Monad-specific method based on [EIP-7966](https://eips.ethereum.org/EIPS/eip-7966). It eliminates the need to poll with [`eth_getTransactionReceipt`](/v1/monad/execution-api/eth_gettransactionreceipt.md) after submission. On Monad, transactions achieve sub-second confirmation due to the chain's architecture, making synchronous receipt return practical.

This method will use `80` [Compute Units](/v1/about/billing.md).

***

## Reference: [Here](https://docs.monad.xyz/reference/rpc-differences)

## **Parameters**

1. `DATA` - The signed transaction data.

```json
params: [
  "0xf86c0a8502540be400825208940123456789abcdef0123456789abcdef0123456789880de0b6b3a764000080820a96a0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1a0b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2",
]
```

## Returns

A transaction receipt object with the following fields:

* `blockHash` - `DATA`, 32 Bytes - hash of the block containing this transaction.
* `blockNumber` - `QUANTITY` - block number where this transaction was included.
* `contractAddress` - `DATA`, 20 Bytes - the contract address created, if the transaction was a contract creation, otherwise `null`.
* `cumulativeGasUsed` - `QUANTITY` - total amount of gas used when this transaction was executed in the block.
* `effectiveGasPrice` - `QUANTITY` - the actual gas price paid per unit of gas.
* `from` - `DATA`, 20 Bytes - address of the sender.
* `gasUsed` - `QUANTITY` - amount of gas used by this specific transaction alone.
* `logs` - `Array` - array of log objects generated by this transaction.
* `logsBloom` - `DATA`, 256 Bytes - bloom filter for light clients to quickly retrieve related logs.
* `status` - `QUANTITY` - `0x1` for success, `0x0` for failure.
* `to` - `DATA`, 20 Bytes - address of the receiver, `null` for contract creation transactions.
* `transactionHash` - `DATA`, 32 Bytes - hash of the transaction.
* `transactionIndex` - `QUANTITY` - index position of the transaction in the block.
* `type` - `QUANTITY` - transaction type (`0x0` for legacy, `0x2` for EIP-1559, etc.).

```json
// Result
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "blockHash": "0xc41f04c4ea63187020ad2c487603e30593f4160e5bc78ffca276413686783569",
    "blockNumber": "0x170d0ca",
    "contractAddress": null,
    "cumulativeGasUsed": "0x5208",
    "effectiveGasPrice": "0x2540be400",
    "from": "0x1234567890abcdef1234567890abcdef12345678",
    "gasUsed": "0x5208",
    "logs": [],
    "logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
    "status": "0x1",
    "to": "0x0123456789abcdef0123456789abcdef01234567",
    "transactionHash": "0xbf93ff41b38fa5e9d0534e462c224e5ad65a1eb7ad7d4e569c98ad94a2c33471",
    "transactionIndex": "0x0",
    "type": "0x2"
  }
}
```

{% tabs %}
{% tab title="mainnet" %}

```bash
curl https://mainnet.monad.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_sendRawTransactionSync","params":["0xSIGNED_TX_DATA"],"id":1}'

```

{% endtab %}

{% tab title="testnet" %}

```bash
curl https://testnet.monad.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_sendRawTransactionSync","params":["0xSIGNED_TX_DATA"],"id":1}'

```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.validationcloud.io/v1/monad/execution-api/eth_sendrawtransactionsync.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.