ETH RPC
The Blockscout ETH RPC API supports 3 methods in the exact format specified for Ethereum nodes, see the Ethereum JSON-RPC Specification for more details. These methods are provided for your convenience. In general, custom RPC methods are recommended.
The following 3 methods are supported:
eth_blockNumber
eth_getBalance
eth_getLogs
In the following examples we use the Ethereum mainnet with the base instance url https://blockscout.com/eth/mainnet
. When sending a request add /api/eth-rpc
to the end of the base url.
eth_blockNumber
Returns the latest block number in the chain in hexidecimal format. No params are needed. Type: POST
Example
eth_getBalance
Returns the balance of a given address in wei. Note the earliest
parameter does not work as expected because genesis block balances are not currently imported. Parameters are required.
Required Parameters
Type | POST |
Data (string) | 20 Byte address to check balance |
Quantity or Tag (string) | Integer value of a block number, or a tag "latest" for the most recent block. |
Example
eth_getLogs
Returns an array of logs matching a specified filter object. Params are optional based on data you want to receive. From more information, see this post on eth_getLogs.
Note: Never returns more than 1000 log entries. You can use pagination options to request the next page. Pagination options params: {"logIndex": "3D", "blockNumber": "6423AC"} which include parameters from the last log received from the previous request. These three parameters are required for pagination.
Parameters
Type | POST |
| 20Byte contract address or list of addresses to collect logs from. |
| Integer block number, |
| Integer block number, |
| Array of 32 Byte |
|
|
Example Query
Last updated