Bloklake

• Backfills and indexers: read every Transfer of a token since deployment in minutes, not days of eth_getLogs pagination.
• Analytics and data pipelines: pull columnar data straight into pandas, Polars, DuckDB or Spark through Apache Arrow, with no hex parsing.
• Wallet and contract activity: every transaction from or to a set of addresses, with their logs, over any range.
• Following the chain: the same query keeps working at the tip, with finality information so you can handle reorgs correctly.

curl https://api.bloklake.com/v1/chains/eth/query/json \
  -H "Authorization: Bearer $BLOKLAKE_API_KEY" \
  -H 'content-type: application/json' \
  -d '{
    "fromBlock": 19426000,
    "toBlock": 19426009,
    "logs": [{"address": ["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"],
              "topic0": ["0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"]}],
    "fields": {"log": {"blockNumber": true, "transactionHash": true, "topic1": true, "topic2": true, "data": true}}
  }'

​

Chains

​

What Bloklake is not

• You can filter logs by address and topic0–topic3, and transactions by from, to, sighash, status and type. Other fields can be returned but not filtered on.
• There is no state (balances, storage, eth_call) and no traces.
• There are no aggregations or joins beyond joinTransactions.