Daily transfer activity
- Gross transfer amount
- 12,500 USDC
- Transfers counted
- 15
- Mint and burn events excluded
- 4
12:00 to 16:00
3,500 USDC- Transfer A
0x5e…21 / event 1 · block 20,862,2141,500 - BurnExcluded by definition
0x2d…80 / event 3 · block 20,862,5403,000 - Transfer B
0x9a…c7 / event 0 · block 20,862,9872,000
Stored through block 20,866,412 Day ends at block 20,865,599 Published
How it comes together
- GraphOps service
- Your systems and team
- GraphOps Substreams
Backfill and follow transfer events
Package output lands in your warehouse with block, transaction, and event index, first for the history you need and then as new blocks arrive.
- Your pipeline
Apply the metric definition
Normalize decimals, exclude mints and burns, count each transaction and event index once, and bucket by UTC time.
- Your pipeline
Check coverage before publishing
Stored output reaches block 20,866,412, past the day’s last block, so your finality policy moves 30 September from provisional to published.
- Your analyst
Answer from the records
The busiest interval, 12:00 to 16:00, holds transfers of 1,500 and 2,000 USDC. A 3,000 USDC burn in the same interval is excluded by the definition.
ResultThe answer names its inputs: 15 transfers counted and 4 mint and burn events excluded, each identified by transaction and event index.
An existing Subgraph can supply the transfers when its schema has them. Keep published results in your own storage so later corrections do not change them.
When a source correction arrives
A reorg can remove or replace a counted transfer. Mark the affected day provisional, regenerate its totals from the corrected records, and keep the previously published figure with its publication time.