Chainstack documentation

# Ethereum eth_getLogs RPC method

Ethereum API method that returns an array of all logs matching a given filter object.

Parameters:

  • object — the filter options:
    • fromBlock — (optional, default: "latest") the integer block number encoded as hexadecimal, or the string with:
      • latest — the latest block that is to be validated. The Beacon Chain may reorg and the latest block can become orphaned.
      • safe — the block that is equal to the tip of the chain and is very unlikely to be orphaned.
      • finalized — the block that is accepted by the two thirds of the Ethereum validators.
      • earliest — the genesis block.
      • pending — the pending state and transactions block.
    • toBlock — (optional, default: "latest") the integer block number encoded as hexadecimal, or the string with:
      • latest — the latest block that is to be validated. The Beacon Chain may reorg and the latest block can become orphaned.
      • safe — the block that is equal to the tip of the chain and is very unlikely to be orphaned.
      • finalized — the block that is accepted by the two thirds of the Ethereum validators.
      • earliest — the genesis block.
      • pending — the pending state and transactions block.
    • address — (optional) the contract address, or a list of addresses from which logs should originate.
    • topics — (optional) the array of DATA topics. Topics are order-dependent. See Ethereum official documentation (opens new window) to learn more about topics.
    • blockhash — (optional) with the addition of EIP-234, blockHash will be a new filter option that restricts the logs returned to the single block with the 32-byte hash blockHash. Using blockHash is equivalent to fromBlock = toBlock = the block number with hash blockHash. If blockHash is present in the filter criteria, then neither fromBlock nor toBlock is allowed.

Returns:

  • array — an array of log objects, or an empty array if nothing has changed since the last poll:
    • removed — the boolean value True if the log was removed due to a chain reorganization. False if it is a valid log.
    • logindex — the integer of the log index position in the block, encoded as hexadecimal. null if pending.
    • transactionindex — the integer of the transactions' index position the log was created from. null if pending.
    • transactionhash — the hash of the transactions the log was created from. null if pending.
    • blockhash — the hash of the block where this log was in. null if pending.
    • blocknumber — the block number where this log was encoded as hexadecimal. null if pending.
    • address — the address from which this log originated.
    • data — contains one or more 32 bytes non-indexed arguments of the log.
    • topics — an array of 0 to 4 32 bytes of indexed log arguments.

Example:

  • web3.js
  • web3.py
  • eth.rb
  • cURL 
const Web3 = require("web3");
const node_url = "CHAINSTACK_NODE_URL";
const web3 = new Web3(node_url);
web3.eth.getPastLogs("0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", (err, logs) => {
    console.log(logs)
})