indexing-blocks

To process every blockchain block for time-series snapshots without contract addresses, you can use an onBlock handler that self-registers without requiring config.yaml entries. This allows block-level aggregation and periodic state capture on EVM chains by exposing block number and timestamp directly to the context.

Yes, you can capture periodic state snapshots on an EVM chain at specific block intervals by configuring the interval parameter. This setting allows you to process every Nth block instead of each block, enabling efficient block-level aggregation for downstream time-series analysis.

The best way to generate hourly volume charts from blockchain block data is by using an onBlock handler to aggregate fees or volume per block. By processing configurable block intervals on EVM chains, you can create periodic snapshots that feed directly into time-series visualizations.

This block indexing approach does not work on non-EVM chains, as it is designed exclusively for Ethereum-compatible networks. It also does not require specific configuration files, as the onBlock handler self-registers without needing any config.yaml entries or contract addresses.

To limit block processing to a specific start and end block range, you can define optional startBlock and endBlock parameters. This bounded processing allows you to constrain time-series snapshot generation to a precise segment of the blockchain.

You should avoid using a block-level handler for time-series data aggregation if you only need to monitor specific smart contract events, as this approach processes blocks globally. It is specifically built for periodic state capture and block-level aggregation rather than isolated contract event tracking.