Skip to main content
Schema: ethereum.nft Table: ez_mev_arbitrage Type: View

What

This table contains the financial metrics from NFT arbitrage transactions including cost, revenue and profits.

Columns

Column NameData TypeDescription
BLOCK_NUMBERNUMBERSequential counter representing the position of a block in the blockchain since genesis (block 0). Key Facts: 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 Usage in Queries: Important: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon.
BLOCK_TIMESTAMPTIMESTAMP_NTZUTC timestamp when the block was produced by validators/miners. Format: TIMESTAMP_NTZ (no timezone) Precision: Second-level accuracy Reliability: Set by block producer Can have minor variations (±15 seconds) Always increasing (newer blocks = later timestamps) Best Practices: Note: Use for time-series analysis, but be aware that block production rates vary by chain.
TX_HASHTEXTUnique 66-character identifier for the transaction. Format: 0x + 64 hexadecimal characters Usage: Primary key for transaction lookups Join key for traces, logs, and token transfers Immutable once confirmed Example: 0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060
MEV_SEARCHERTEXTThe address of the MEV finder, taken from the origin address that initiated the transaction
MEV_CONTRACTTEXTThe contract address that the MEV searcher uses to execute mev transactions, taken from the origin to address of the transaction
COST_USDFLOATThe total cost in USD to purchase the NFT(s) in the transaction
REVENUE_USDFLOATThe total revenue in USD from selling the NFT(s) and other related tokens in the transaction
MINER_TIP_USDFLOATThe total amount in USD sent to the block miner/builder as a tip to include the transaction in the block
TX_FEE_USDFLOATThe transaction fee in USD terms
PROFIT_USDFLOATThe remainder in USD after subtracting cost, miner tip and transaction fee from revenue
FUNDING_SOURCETEXTThe source of the funds used to perform the arbitrage. Currently there are three sources. Existing funds indicate that the user uses funds that are already in their balance while flash loan and flash swaps indicate that the user took a flash loan in the transaction
ARBITRAGE_DIRECTIONTEXTThe direction in which the arbitrage is performed. There are two possibilities of origin and destination: pool and marketplace. Pool represents marketplaces like nftx and sudoswap where users swap from a pool whereas marketplace represents regular marketplaces that are not pool-based
EZ_MEV_ARBITRAGE_IDTEXTPrimary key - unique identifier for each row ensuring data integrity. Format: Usually VARCHAR containing composite key generated using MD5 hash of the relevant columns. Example: MD5(blocknumber, txhash, trace_index) Usage: Deduplication in incremental loads Join operations for data quality checks Troubleshooting specific records Important: Implementation varies by table - check table-specific documentation.
INSERTED_TIMESTAMPTIMESTAMP_NTZUTC timestamp when the record was first added to the Flipside database. Format: TIMESTAMP_NTZ Use Cases: Data freshness monitoring Incremental processing markers Debugging data pipeline issues SLA tracking Query Example:
MODIFIED_TIMESTAMPTIMESTAMP_NTZUTC timestamp of the most recent update to this record. Format: TIMESTAMP_NTZ Triggers for Updates: Data corrections Enrichment additions Reprocessing for accuracy Schema migrations Monitoring Usage: