Filters and block batches

Choose a field, an operator, and a value. Available operators include equality, inequality, numeric comparisons, and in. Use the operator suitable for the field.

Use decimal token units for Value and check raw decoded arguments separately. A missing USD estimate is not zero. Avoid requiring a dollar threshold for assets whose example has no valuation.

AND requires both groups to match. Consecutive OR rows form an alternative group, and groups are joined with AND.

For example: From is wallet · OR To is wallet · AND Value ≥ 1000 selects transfers involving the wallet in either direction, with at least 1000 tokens.

Path conditions require all their conditions to match. Use separate paths for separate outcomes, remembering that both paths run if both match.

Fields can refer to nested data, such as args.value or logs.0.args.value. Numeric segments refer to array positions, starting at zero. An exact log position is not guaranteed to have the same meaning in every transaction; check representative examples.

Where offered for transfers, batching combines matching events on the same chain and in the same block. Trigger filters apply to individual events before grouping. The path receives the resulting batch.

A batch has count and events, plus summary fields. It has no single transaction hash. Use explorer_block_url for the block and events for individual transfers.

For token batches, value_decimal adds the token amounts, so it is only meaningful as one asset total when the batch contains the same asset. USD totals can be partial when some events lack a valuation.

After changing batching, inspect the event fields and rerun the test. A template written for one transfer may no longer apply.