TRANSACTION DATA[required] - The signed transaction data.
EXAMPLE
Explain## JSON-RPC over HTTPS POST
### The below code sample will fail with "nonce too low" - this is expected because the param represents old transaction data
curl https://mainet.rpc.aarmascan.com
-X POST \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_sendRawTransaction","params": ["0xf869018203e882520894f17f52151ebef6c7334fad080c5704d77216b732881bc16d674ec80000801ba02da1c48b670996dcb1f447ef9ef00b33033c48a4fe938f420bec3e56bfd24071a062e0aa78a81bf0290afbc3a9d8e9a068e6d74caa66c5e0fa8a46deaae96b0833"],"id":1}'
## JSON-RPC over WSS
wscat -c ws://mainet.rpc.aarmascan.com
>{"jsonrpc":"2.0","method":"eth_sendRawTransaction","params":["0xd46e8dd67c5d32be8d46e8dd67c5d32be8058bb8eb970870f072445675058bb8eb970870f072445675"],"id":1}
RESPONSE
RESULT FIELDS
TRANSACTION HASH - 32 Bytes - the transaction hash, or the zero hash if the transaction is not yet available
NOTE - Use eth_getTransactionReceipt to get the contract address, after the transaction was mined, when you created a contract.
On Mainnet, Rinkeby, Ropsten and Goerli, if this call causes the EVM to execute a REVERT operation, an error response of the following form is returned, with the revert reason pre-decoded as a string (not yet supported on Kovan):