eth_getFilterLogs

Returns an array of all logs matching filter with given id.

REQUEST PARAMS

  • FILTER OBJECT

    • fromBlock[optional, default: "latest"] hexadecimal block number, or "latest" for the last mined block. The "pending" option is not currently supported.

    • toBlock[optional, default: "latest"] hexadecimal block number, or "latest" for the last mined block.

    • address: [optional] (20 Bytes) Contract address or a list of addresses from which logs should originate.

    • topics: [optional] Array of 32 Bytes DATA topics. Topics are order-dependent. Each topic can also be an array of DATA with "or" options.

    • blockhash: [optional] With the addition of EIP-234, blockHash 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 are allowed.

EXAMPLE

## JSON-RPC over HTTPS POST
## Replace YOUR-API-KEY with an API key from your chainRPC Dashboard
## You can also replace mainnet with a different supported network
curl https://eth.chainrpc.io/v3/YOUR-API-KEY \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getFilterLogs","params":["0x10ff0bfbedb01f0dbd4106d14eb719ec38b6eb5b821c"],"id":1}'

## JSON-RPC over WSS
## Replace YOUR-API-KEY with an API key from your chainRPC Dashboard
## You can also replace mainnet with a different supported network
wscat -c wss://eth.chainrpc.io/v3/YOUR-API-KEY
>{"jsonrpc":"2.0","method":"eth_getFilterLogs","params":["0x10ff0bfbedb01f0dbd4106d14eb719ec38b6eb5b821c"],"id":1}

RESPONSE

RESULT FIELDS

  • LOG OBJECT ARRAY - Array of log objects, or an empty array if nothing has changed since last poll.

    • logs are objects with following params:

  • removed: true when the log was removed, due to a chain reorganization. false if its a valid log.

  • logIndex: hexadecimal of the log index position in the block. null when its pending log.

  • transactionIndex: hexadecimal of the transactions index position log was created from. null when its pending log.

  • transactionHash: 32 Bytes - hash of the transactions this log was created from. null when its pending log.

  • blockHash: 32 Bytes - hash of the block where this log was in. null when its pending. null when its pending log.

  • blockNumber: the block number where this log was in. null when its pending. null when its pending log.

  • address: 20 Bytes - address from which this log originated.

  • data: DATA - contains the non-indexed arguments of the log.

  • topics: Array of DATA - Array of 0 to 4 32 Bytes DATA of indexed log arguments. (In solidity: The first topic is the hash of the signature of the event (e.g. Deposit(address,bytes32,uint256)), except you declared the event with the anonymous specifier.)

BODY

Previouseth_newPendingTransactionFilterNexteth_getFilterChanges

Last updated