arbitrum.core Table: ez_native_transfers Type: Base Table
What
This convenience table tracks all native asset transfers (ETH, AVAX, MATIC, etc.) extracted from transaction traces. It provides a simplified view of value movements with decimal adjustments and USD conversions, making it easy to analyze fund flows without parsing complex trace data.Key Use Cases
- Tracking native asset movements between wallets and contracts
- Analyzing exchange deposits and withdrawals
- Monitoring whale movements and large transfers
- Calculating wallet balances from transfer history
- Identifying internal transfers within smart contract executions
Important Relationships
- Join with fact_transactions: Use
tx_hashfor transaction context - Join with fact_traces: Use
tx_hashandtrace_indexfor trace details - Join with dim_labels: Use addresses for entity identification
- Complement to ez_token_transfers: This table for native, that for tokens
Commonly-used Fields
from_address: The sender of the native asset transferto_address: The recipient of the native asset transferamount: Decimal-adjusted transfer amountamount_usd: USD value at time of transferorigin_from_address: Original transaction senderorigin_to_address: Original transaction recipientidentifier: Trace identifier (0 for external transfers)
Sample queries
Daily Native Asset Transfer VolumeColumns
| Column Name | Data Type | Description |
|---|---|---|
| BLOCK_NUMBER | NUMBER | Sequential counter representing the position of a block in the blockchain since genesis (block 0). |
- Immutable once finalized
- Primary ordering mechanism for blockchain data
- Increments by 1 for each new block
- Used as a proxy for time in many analyses
- Set by block producer
- Can have minor variations (±15 seconds)
- Always increasing (newer blocks = later timestamps)
- Primary key for transaction lookups
- Join key for traces, logs, and token transfers
- Immutable once confirmed
0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060 | | TX_POSITION |
NUMBER | Zero-indexed position of transaction within its block.
Insights:
- Position 0: First transaction in block
- MEV bots often target early positions
- Bundle transactions appear consecutively
- Useful for analyzing transaction ordering | | TRACE_INDEX | NUMBER | Sequential index of trace within the transaction’s execution.
- Always 42 characters (0x + 40 hex chars)
- Lowercase normalized in all tables
- Cannot be NULL for valid transactions
- For contract creation: sender of creation transaction
- EOA → EOA: Simple transfer
- EOA → Contract: User interaction
- Contract → Contract: Internal calls (see fact_traces)
- Known addresses: Exchange hot wallets, protocol deployers
- 0xa9059cbb: transfer(address,uint256)
- 0x095ea7b3: approve(address,uint256)
- 0x23b872dd: transferFrom(address,address,uint256)
- Deduplication in incremental loads
- Join operations for data quality checks
- Troubleshooting specific records
- Data freshness monitoring
- Incremental processing markers
- Debugging data pipeline issues
- SLA tracking