POST
/
efb0a5eccd2caa5135eb54eba6f7f300
eth_getLogs
curl --request POST \
  --url https://optimism-mainnet.core.chainstack.com/efb0a5eccd2caa5135eb54eba6f7f300 \
  --header 'Content-Type: application/json' \
  --data '{
  "jsonrpc": "2.0",
  "method": "eth_getLogs",
  "id": 1,
  "params": [
    {
      "fromBlock": "latest",
      "address": "0x350a791Bfc2C21F9Ed5d10980Dad2e2638ffa7f6",
      "topics": [
        "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"
      ]
    }
  ]
}'
{
  "jsonrpc": "<string>",
  "id": 123,
  "result": [
    {
      "removed": true,
      "logIndex": "<string>",
      "transactionIndex": "<string>",
      "transactionHash": "<string>",
      "blockHash": "<string>",
      "blockNumber": "<string>",
      "address": "<string>",
      "data": "<string>",
      "topics": [
        "<string>"
      ]
    }
  ]
}
Optimism API method eth_getLogs retrieves logs matching specific criteria, such as block range, address, and topics. This method is crucial for applications that need to fetch log data for analysis, display, or monitoring smart contract events. The example track Chainlink token transfers.
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

  • filterObject — an object containing filter options:
    • fromBlock — the starting block to search for logs. In this example, it’s set to "latest".
    • address — the contract address to fetch logs from.
    • topics — an array of topics to match against the logs.

​
Response

  • result — an array of log objects. Each log object contains details such as whether the log was removed (due to a chain reorganization), log index, transaction index, transaction hash, block hash, block number, address from which the log originated, data contained in the log, and topics associated with the log.

​
Use case

The eth_getLogs method is essential for:
  • DApps that require access to historical log data for analysis or display purposes.
  • Services that monitor smart contract interactions over time, needing to retrieve all past events that match certain criteria.
  • Analytical tools that process and visualize blockchain data based on logs from specific contracts or transactions.

Body

application/json

Response

200 - application/json

Logs matching the criteria

The response is of type object.