eth_sendRawTransaction

EthereumC1

Submits a signed, RLP-encoded transaction for inclusion. Returns the transaction hash on acceptance into the mempool; signing happens client-side, keys never leave your infrastructure.

Endpoint

POST https://api.1st-node.com/v1/ethereum/rpc

Parameters

Name	Type	Description
signedTx	DATA	The signed, RLP-encoded transaction.

Returns

DATA, 32 bytes — the transaction hash.

Request

curl https://api.1st-node.com/v1/ethereum/rpc \
  -H "Authorization: Bearer $ONE_KEY" \
  -H "content-type: application/json" \
  -d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_sendRawTransaction",
  "params": ["0xf86c808504a817c800825208…"]
}'

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_sendRawTransaction",
  "params": ["0xf86c808504a817c800825208…"]
}

Response

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0x88df016429689c079f3b2f6ad39fa052532c56795b733da78a91ebe6a713944b"
}

More transactions methods on Ethereum

eth_getTransactionByHash eth_getTransactionReceipt eth_call eth_estimateGas

← Ethereum API

よくある質問

Do you hold my private keys?

No — transactions are signed client-side; only the signed payload is broadcast.

チャージして、キーを取得し、リリース。

セルフサーブ。暗号資産またはカードで支払い。クレジットで従量課金——重いプリミティブは高く、単純なものは安価。

APIキーを取得