# Table of Contents - [What is FlipsideAI? - Flipside Docs](#what-is-flipsideai-flipside-docs) - [Dim Labels - Flipside Docs](#dim-labels-flipside-docs) - [Dim Programs - Flipside Docs](#dim-programs-flipside-docs) - [Defi - Flipside Docs](#defi-flipside-docs) - [Fact Liquidity Pool Actions - Flipside Docs](#fact-liquidity-pool-actions-flipside-docs) - [Aleo Data - Flipside Docs](#aleo-data-flipside-docs) - [Fact Swaps - Flipside Docs](#fact-swaps-flipside-docs) - [Dim Token Registrations - Flipside Docs](#dim-token-registrations-flipside-docs) - [Fact Block Solutions - Flipside Docs](#fact-block-solutions-flipside-docs) - [Fact Block Round Batches - Flipside Docs](#fact-block-round-batches-flipside-docs) - [Fact Transitions - Flipside Docs](#fact-transitions-flipside-docs) - [Fact Blocks - Flipside Docs](#fact-blocks-flipside-docs) - [Core Tables - Flipside Docs](#core-tables-flipside-docs) - [Fact Transfers - Flipside Docs](#fact-transfers-flipside-docs) - [Fact Transactions - Flipside Docs](#fact-transactions-flipside-docs) - [Ez Prices Hourly - Flipside Docs](#ez-prices-hourly-flipside-docs) - [Ez Asset Metadata - Flipside Docs](#ez-asset-metadata-flipside-docs) - [Fact Prices Ohlc Hourly - Flipside Docs](#fact-prices-ohlc-hourly-flipside-docs) - [Ez Core Metrics Hourly - Flipside Docs](#ez-core-metrics-hourly-flipside-docs) - [Stats - Flipside Docs](#stats-flipside-docs) - [Price - Flipside Docs](#price-flipside-docs) - [Ez Lending Ohlc Rates - Flipside Docs](#ez-lending-ohlc-rates-flipside-docs) - [Fact Vat File - Flipside Docs](#fact-vat-file-flipside-docs) - [Fact Vat Flux - Flipside Docs](#fact-vat-flux-flipside-docs) - [Fact Vat Fold - Flipside Docs](#fact-vat-fold-flipside-docs) - [Fact Vat Fork - Flipside Docs](#fact-vat-fork-flipside-docs) - [Fact Vat Frob - Flipside Docs](#fact-vat-frob-flipside-docs) - [Fact Vat Slip - Flipside Docs](#fact-vat-slip-flipside-docs) - [Fact Vat Move - Flipside Docs](#fact-vat-move-flipside-docs) - [Fact Vat Suck - Flipside Docs](#fact-vat-suck-flipside-docs) - [Dim Nft Collection Metadata - Flipside Docs](#dim-nft-collection-metadata-flipside-docs) - [Ez Lending Loans - Flipside Docs](#ez-lending-loans-flipside-docs) - [Ez Lending Liquidations - Flipside Docs](#ez-lending-liquidations-flipside-docs) - [Maker - Flipside Docs](#maker-flipside-docs) - [Ez Mev Arbitrage - Flipside Docs](#ez-mev-arbitrage-flipside-docs) - [Ez Lending Repayments - Flipside Docs](#ez-lending-repayments-flipside-docs) - [Ez Nft Sales - Flipside Docs](#ez-nft-sales-flipside-docs) - [Ez Nft Transfers - Flipside Docs](#ez-nft-transfers-flipside-docs) - [Fact Mev Arbitrage Events - Flipside Docs](#fact-mev-arbitrage-events-flipside-docs) - [Nft - Flipside Docs](#nft-flipside-docs) - [Ethereum Onchain Data - Flipside Docs](#ethereum-onchain-data-flipside-docs) - [Dim Asset Metadata - Flipside Docs](#dim-asset-metadata-flipside-docs) - [Ez Asset Metadata - Flipside Docs](#ez-asset-metadata-flipside-docs) - [Ez Prices Hourly - Flipside Docs](#ez-prices-hourly-flipside-docs) - [Fact Prices Ohlc Hourly - Flipside Docs](#fact-prices-ohlc-hourly-flipside-docs) - [Price - Flipside Docs](#price-flipside-docs) - [Dim Nfl Teams - Flipside Docs](#dim-nfl-teams-flipside-docs) - [Dim Nfl Athletes - Flipside Docs](#dim-nfl-athletes-flipside-docs) - [Dim Nflad Playoff Rosters - Flipside Docs](#dim-nflad-playoff-rosters-flipside-docs) - [Ez Moment Player Ids - Flipside Docs](#ez-moment-player-ids-flipside-docs) - [Beta - Flipside Docs](#beta-flipside-docs) - [Dim Contract Abis - Flipside Docs](#dim-contract-abis-flipside-docs) - [Dim Contracts - Flipside Docs](#dim-contracts-flipside-docs) - [Dim Labels - Flipside Docs](#dim-labels-flipside-docs) - [Ez Decoded Event Logs - Flipside Docs](#ez-decoded-event-logs-flipside-docs) - [Ez Native Transfers - Flipside Docs](#ez-native-transfers-flipside-docs) - [Ez Token Transfers - Flipside Docs](#ez-token-transfers-flipside-docs) - [Fact Blocks - Flipside Docs](#fact-blocks-flipside-docs) - [Fact Traces - Flipside Docs](#fact-traces-flipside-docs) - [Fact Event Logs - Flipside Docs](#fact-event-logs-flipside-docs) - [Fact Transactions - Flipside Docs](#fact-transactions-flipside-docs) - [Core Evm - Flipside Docs](#core-evm-flipside-docs) - [Dim Address Mapping - Flipside Docs](#dim-address-mapping-flipside-docs) - [Dim Contract Labels - Flipside Docs](#dim-contract-labels-flipside-docs) - [Dim Labels - Flipside Docs](#dim-labels-flipside-docs) - [Ez Token Transfers - Flipside Docs](#ez-token-transfers-flipside-docs) - [Ez Transaction Actors - Flipside Docs](#ez-transaction-actors-flipside-docs) - [Fact Blocks - Flipside Docs](#fact-blocks-flipside-docs) - [Fact Account Storage - Flipside Docs](#fact-account-storage-flipside-docs) - [Core Tables - Flipside Docs](#core-tables-flipside-docs) - [Fact Events - Flipside Docs](#fact-events-flipside-docs) - [Fact Transactions - Flipside Docs](#fact-transactions-flipside-docs) - [Gov - Flipside Docs](#gov-flipside-docs) - [Dim Validator Labels - Flipside Docs](#dim-validator-labels-flipside-docs) - [Defi - Flipside Docs](#defi-flipside-docs) - [Ez Staking Actions - Flipside Docs](#ez-staking-actions-flipside-docs) - [Dim Swap Pool Labels - Flipside Docs](#dim-swap-pool-labels-flipside-docs) - [Ez Bridge Activity - Flipside Docs](#ez-bridge-activity-flipside-docs) - [Ez Dex Swaps - Flipside Docs](#ez-dex-swaps-flipside-docs) - [Fact Bridge Activity - Flipside Docs](#fact-bridge-activity-flipside-docs) - [Fact Dex Swaps - Flipside Docs](#fact-dex-swaps-flipside-docs) - [Nft - Flipside Docs](#nft-flipside-docs) - [Dim Asset Metadata - Flipside Docs](#dim-asset-metadata-flipside-docs) - [Ez Asset Metadata - Flipside Docs](#ez-asset-metadata-flipside-docs) - [Dim Moment Metadata - Flipside Docs](#dim-moment-metadata-flipside-docs) - [Dim Ufc Strike Metadata - Flipside Docs](#dim-ufc-strike-metadata-flipside-docs) - [Dim Allday Metadata - Flipside Docs](#dim-allday-metadata-flipside-docs) - [Ez Nft Sales - Flipside Docs](#ez-nft-sales-flipside-docs) - [Fact Prices Ohlc Hourly - Flipside Docs](#fact-prices-ohlc-hourly-flipside-docs) - [Flow Data - Flipside Docs](#flow-data-flipside-docs) - [Stats - Flipside Docs](#stats-flipside-docs) - [Ez Prices Hourly - Flipside Docs](#ez-prices-hourly-flipside-docs) - [Dim Storefront Items - Flipside Docs](#dim-storefront-items-flipside-docs) - [Price - Flipside Docs](#price-flipside-docs) - [Fact Points Transfers - Flipside Docs](#fact-points-transfers-flipside-docs) - [Fact Points Balances - Flipside Docs](#fact-points-balances-flipside-docs) - [Gov - Flipside Docs](#gov-flipside-docs) - [Fact Delegations - Flipside Docs](#fact-delegations-flipside-docs) - [Ez Lending Ohlc Rates - Flipside Docs](#ez-lending-ohlc-rates-flipside-docs) - [Defi - Flipside Docs](#defi-flipside-docs) - [Ez Nft Transfers - Flipside Docs](#ez-nft-transfers-flipside-docs) - [Ez Nft Sales - Flipside Docs](#ez-nft-sales-flipside-docs) - [Nft - Flipside Docs](#nft-flipside-docs) - [Dim Asset Metadata - Flipside Docs](#dim-asset-metadata-flipside-docs) - [Fact Governance Proposal Deposits - Flipside Docs](#fact-governance-proposal-deposits-flipside-docs) - [Fact Governance Submit Proposal - Flipside Docs](#fact-governance-submit-proposal-flipside-docs) - [Fact Governance Votes - Flipside Docs](#fact-governance-votes-flipside-docs) - [Gov - Flipside Docs](#gov-flipside-docs) - [Dim Prices - Flipside Docs](#dim-prices-flipside-docs) - [Osmosis Data - Flipside Docs](#osmosis-data-flipside-docs) - [Ez Prices - Flipside Docs](#ez-prices-flipside-docs) - [Price - Flipside Docs](#price-flipside-docs) - [Ez Core Metrics Hourly - Flipside Docs](#ez-core-metrics-hourly-flipside-docs) - [Stats - Flipside Docs](#stats-flipside-docs) - [Balances - Flipside Docs](#balances-flipside-docs) - [Ez Balances Erc20 Daily - Flipside Docs](#ez-balances-erc20-daily-flipside-docs) - [Dim Contract Abis - Flipside Docs](#dim-contract-abis-flipside-docs) - [Ez Balances Native Daily - Flipside Docs](#ez-balances-native-daily-flipside-docs) - [Dim Contracts - Flipside Docs](#dim-contracts-flipside-docs) - [Dim Labels - Flipside Docs](#dim-labels-flipside-docs) - [Ez Decoded Event Logs - Flipside Docs](#ez-decoded-event-logs-flipside-docs) - [Ez Native Transfers - Flipside Docs](#ez-native-transfers-flipside-docs) - [Fact Blocks - Flipside Docs](#fact-blocks-flipside-docs) - [Ez Token Transfers - Flipside Docs](#ez-token-transfers-flipside-docs) - [Fact Event Logs - Flipside Docs](#fact-event-logs-flipside-docs) - [Core Tables - Flipside Docs](#core-tables-flipside-docs) - [Dim Dex Liquidity Pools - Flipside Docs](#dim-dex-liquidity-pools-flipside-docs) - [Fact Traces - Flipside Docs](#fact-traces-flipside-docs) - [Fact Transactions - Flipside Docs](#fact-transactions-flipside-docs) - [Ez Lending Ohlc Rates - Flipside Docs](#ez-lending-ohlc-rates-flipside-docs) - [Ez Bridge Activity - Flipside Docs](#ez-bridge-activity-flipside-docs) - [Ez Dex Swaps - Flipside Docs](#ez-dex-swaps-flipside-docs) - [Ez Lending Flashloans - Flipside Docs](#ez-lending-flashloans-flipside-docs) - [Ez Lending Borrows - Flipside Docs](#ez-lending-borrows-flipside-docs) - [Ez Lending Deposits - Flipside Docs](#ez-lending-deposits-flipside-docs) - [Ez Lending Liquidations - Flipside Docs](#ez-lending-liquidations-flipside-docs) - [Nft - Flipside Docs](#nft-flipside-docs) - [Page Not Found](#page-not-found) --- # What is FlipsideAI? - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/flipsideai#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... Ctrl KAsk AI Search... Navigation Getting Started What is FlipsideAI? [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [How it works](https://docs.flipsidecrypto.xyz/flipsideai#how-it-works) * [Get started](https://docs.flipsidecrypto.xyz/flipsideai#get-started) * [Key features](https://docs.flipsidecrypto.xyz/flipsideai#key-features) * [Reference data with Mentions](https://docs.flipsidecrypto.xyz/flipsideai#reference-data-with-mentions) * [Customize with Rules](https://docs.flipsidecrypto.xyz/flipsideai#customize-with-rules) * [Work in teams](https://docs.flipsidecrypto.xyz/flipsideai#work-in-teams) * [Sophisticated analysis, made easy](https://docs.flipsidecrypto.xyz/flipsideai#sophisticated-analysis%2C-made-easy) * [FlipAI Agents: Data science in your pocket](https://docs.flipsidecrypto.xyz/flipsideai#flipai-agents%3A-data-science-in-your-pocket) * [Share your work](https://docs.flipsidecrypto.xyz/flipsideai#share-your-work) * [Download your data](https://docs.flipsidecrypto.xyz/flipsideai#download-your-data) * [Run queries directly](https://docs.flipsidecrypto.xyz/flipsideai#run-queries-directly) * [Add your own data](https://docs.flipsidecrypto.xyz/flipsideai#add-your-own-data) * [Pro tips](https://docs.flipsidecrypto.xyz/flipsideai#pro-tips) * [Next steps](https://docs.flipsidecrypto.xyz/flipsideai#next-steps) FlipsideAI is an AI-powered blockchain intelligence platform originally built to supercharge the Flipside Data Science team—now available to everyone. It combines leading language models (GPT, Claude, Gemini) with Flipside’s unmatched blockchain data across 30+ networks and 7+ trillion data points. From granular transaction-level detail to aggregate metrics like TVL, FlipsideAI opens up a whole new way to engage with data and get the intelligence you need. [​](https://docs.flipsidecrypto.xyz/flipsideai#how-it-works) How it works ---------------------------------------------------------------------------- 1 Ask a question Ask about a token, application, protocol, chain, stablecoins—whatever’s on your mind. 2 FlipsideAI analyzes FlipsideAI formulates a plan, writes queries, runs analyses, and generates outputs (text, graphs, tables). 3 Iterate and share Keep the conversation going with follow-ups or share your findings. **Pro tip:** Treat it like a conversation, not a one-off. The more context you bring, the better the results. **Always specify which chain(s) and contract(s) you want to analyze**—if you know them, tell FlipsideAI explicitly. [​](https://docs.flipsidecrypto.xyz/flipsideai#get-started) Get started -------------------------------------------------------------------------- Ready to dive in? Jump to [Quickstart](https://docs.flipsidecrypto.xyz/flipsideai/quickstart) to start chatting. Not sure where to begin? Try these: [Browse prompt library\ ---------------------\ \ Explore example prompts and analyses built by the community.](https://science.flipsidecrypto.xyz/built-by-ai/) Ask about a protocol -------------------- Ask the chat what it knows about a blockchain, protocol, or token you’re curious about. [Learn prompting\ ---------------\ \ Master the art of asking effective questions.](https://docs.flipsidecrypto.xyz/flipsideai/prompting) [Try FlipAI Agents\ -----------------\ \ Use specialized AI-assistants to solve specific problems in minutes.](https://docs.flipsidecrypto.xyz/flipsideai/agents) [​](https://docs.flipsidecrypto.xyz/flipsideai#key-features) Key features ---------------------------------------------------------------------------- ### [​](https://docs.flipsidecrypto.xyz/flipsideai#reference-data-with-mentions) Reference data with Mentions Use the `@` symbol to reference specific **datasets** and **workflows** in your conversations. This helps FlipsideAI understand exactly which data sources you want to work with.[Learn about Mentions\ --------------------\ \ Reference datasets and workflows in chat](https://docs.flipsidecrypto.xyz/flipsideai/mentions) ### [​](https://docs.flipsidecrypto.xyz/flipsideai#customize-with-rules) Customize with Rules Tweak the chat’s behavior with **Rules** to set personality, style, and response patterns.[Learn about Rules\ -----------------\ \ Customize your FlipsideAI experience](https://docs.flipsidecrypto.xyz/flipsideai/rules) ### [​](https://docs.flipsidecrypto.xyz/flipsideai#work-in-teams) Work in teams Use **Teams** to share your work with colleagues and collaborate on analyses.[Team collaboration\ ------------------\ \ Set up team workspaces](https://docs.flipsidecrypto.xyz/flipsideai/teams) ### [​](https://docs.flipsidecrypto.xyz/flipsideai#sophisticated-analysis,-made-easy) Sophisticated analysis, made easy We’ve trained specialized **Workflows** (aka “Agents”) on complex analytical topics. Unlike open-ended questions, Workflows guide you with pre-trained, state-of-the-art methods to get to the best answer faster.[Explore Workflows\ -----------------\ \ Discover specialized analysis agents](https://docs.flipsidecrypto.xyz/flipsideai/workflows) ### [​](https://docs.flipsidecrypto.xyz/flipsideai#flipai-agents:-data-science-in-your-pocket) FlipAI Agents: Data science in your pocket Expert AI-assistants trained by data scientists to solve specific problems. Each agent guides you through structured workflows with purpose-built interfaces—no coding or analytics expertise required. Whether you’re building wallet audiences, analyzing competitors, or optimizing airdrops, Agents combine proprietary methodologies, cross-chain data, and blockchain-native AI to deliver actionable insights in minutes.[Explore FlipAI Agents\ ---------------------\ \ Discover specialized agents for wallet targeting, competitive intelligence, and more](https://docs.flipsidecrypto.xyz/flipsideai/agents) ### [​](https://docs.flipsidecrypto.xyz/flipsideai#share-your-work) Share your work * Make any chat public via the purple **Share** button in the top right * Publish and share artifacts/reports with the **Publish Artifact** button [Sharing & exporting\ -------------------\ \ Learn how to share your analyses](https://docs.flipsidecrypto.xyz/flipsideai/sharing) ### [​](https://docs.flipsidecrypto.xyz/flipsideai#download-your-data) Download your data Every query is transparent. Click any Flipside Data box → expand the query → download results as CSV. ### [​](https://docs.flipsidecrypto.xyz/flipsideai#run-queries-directly) Run queries directly Already know your query? Paste it into chat—FlipsideAI will run it directly. Then summarize, analyze, and share as usual. ### [​](https://docs.flipsidecrypto.xyz/flipsideai#add-your-own-data) Add your own data Upload a CSV to analyze on its own, or join it with Flipside data. (Uploads stay private to you.) [​](https://docs.flipsidecrypto.xyz/flipsideai#pro-tips) Pro tips -------------------------------------------------------------------- It's a conversation See something weird, unexpected, or interesting? Ask! The back-and-forth is where the magic happens. Ask for what you want Tell the chat how you want outputs styled: colors, chart types, Twitter-ready visuals—even upload an inspo image. Found a style you love? Save it in a Rule for consistent results. Remember: LLMs are math, not people Workflows are structured, quasi-deterministic methodologies. Running the same question in Workflow mode vs general chat will give you different results—by design. [​](https://docs.flipsidecrypto.xyz/flipsideai#next-steps) Next steps ------------------------------------------------------------------------ [Quickstart guide\ ----------------\ \ Get up and running in minutes](https://docs.flipsidecrypto.xyz/flipsideai/quickstart) [Effective prompting\ -------------------\ \ Learn to ask better questions](https://docs.flipsidecrypto.xyz/flipsideai/prompting) [Analysis modes\ --------------\ \ Understand how FlipsideAI thinks](https://docs.flipsidecrypto.xyz/flipsideai/analysis-modes) [Working with data\ -----------------\ \ Validate and export your results](https://docs.flipsidecrypto.xyz/flipsideai/data-and-results) [FlipAI Agents\ -------------\ \ Use specialized AI-assistants to solve specific problems](https://docs.flipsidecrypto.xyz/flipsideai/agents) Was this page helpful? YesNo [Quickstart](https://docs.flipsidecrypto.xyz/flipsideai/quickstart) Ctrl+I Assistant Responses are generated using AI and may contain mistakes. --- # Dim Labels - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-labels#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Dim Labels [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-labels#columns) **Schema**: `aleo.core` **Table**: `dim_labels` **Type**: Base Table A hand curated table containing address names / labels for popular contracts, validators, tokens, etc. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-labels#columns) Columns -------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCKCHAIN | TEXT | The name of the blockchain | | CREATOR | TEXT | The name of the creator of the label | | ADDRESS | TEXT | Address that the label is for. This is the field that should be used to join other tables with labels. | | ADDRESS\_NAME | TEXT | The name associated with the address | | LABEL\_TYPE | TEXT | A high-level category describing the addresses main function or ownership | | LABEL\_SUBTYPE | TEXT | A sub-category nested within label type providing further detail | | PROJECT\_NAME | TEXT | Name of the project or entity associated with the address | | DIM\_LABELS\_ID | TEXT | Unique identifier for each label record | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | Was this page helpful? YesNo [Core Tables](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/overview) [Dim Programs](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-programs) ⌘I --- # Dim Programs - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-programs#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Dim Programs [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-programs#columns) **Schema**: `aleo.core` **Table**: `dim_programs` **Type**: Base Table Dimension table containing information about programs deployed on the network. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-programs#columns) Columns ---------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | DEPLOYMENT\_BLOCK\_ID | NUMBER | The ID of the block in which this program was deployed. | | DEPLOYMENT\_BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp of the block in which this program was deployed. | | PROGRAM\_ID | TEXT | The identifier of the program associated with this transition. | | EDITION | NUMBER | The edition number of the program. | | PROGRAM | TEXT | The full program code as a string. | | VERIFYING\_KEYS | VARIANT | The verifying keys associated with the program, used for cryptographic verification. | | DIM\_PROGRAM\_ID | TEXT | | | INSERT\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | | INVOCATION\_ID | TEXT | | Was this page helpful? YesNo [Dim Labels](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-labels) [Dim Token Registrations](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-token-registrations) ⌘I --- # Defi - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Defi [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/overview#overview) Overview -------------------------------------------------------------------------------------------- This schema contains 2 tables and views for Aleo data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/overview#tables-and-views) Tables and Views ------------------------------------------------------------------------------------------------------------ [Fact Liquidity Pool Actions\ ---------------------------\ \ Records of all liquidity pool actions on Aleo, including adding and removing liquidity.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/fact-liquidity-pool-actions) [Fact Swaps\ ----------\ \ Records of all swap transactions on Aleo, including both public and private swaps.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/fact-swaps) Was this page helpful? YesNo [Fact Transitions](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transitions) [Fact Liquidity Pool Actions](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/fact-liquidity-pool-actions) ⌘I --- # Fact Liquidity Pool Actions - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/fact-liquidity-pool-actions#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Fact Liquidity Pool Actions [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/fact-liquidity-pool-actions#columns) **Schema**: `aleo.defi` **Table**: `fact_liquidity_pool_actions` **Type**: Base Table Records of all liquidity pool actions on Aleo, including adding and removing liquidity. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/fact-liquidity-pool-actions#columns) Columns ------------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp at which the block began. | | BLOCK\_ID | NUMBER | The block height the block was recorded at. | | TX\_ID | TEXT | The unique identifier for the transaction. | | SUCCEEDED | BOOLEAN | A boolean value indicating if the event succeeded. | | ROOT\_ACTION | TEXT | The program and function that initiated the liquidity pool action | | LIQUIDITY\_ACTION | TEXT | The type of liquidity action performed (e.g., add, remove) | | LIQUIDITY\_PROVIDER | TEXT | The address that performed the liquidity pool action | | TOKEN1\_ID | TEXT | The token id of the first token in the liquidity pair | | TOKEN1\_SYMBOL | TEXT | The symbol of the first token in the liquidity pair | | TOKEN1\_AMOUNT\_UNADJ | NUMBER | The amount of the first token added or removed from the pool, unadjusted for decimals | | TOKEN1\_AMOUNT | FLOAT | The amount of the first token added or removed from the pool, adjusted for decimals | | TOKEN2\_ID | TEXT | The token id of the second token in the liquidity pair | | TOKEN2\_SYMBOL | TEXT | The symbol of the second token in the liquidity pair | | TOKEN2\_AMOUNT\_UNADJ | NUMBER | The amount of the second token added or removed from the pool, unadjusted for decimals | | TOKEN2\_AMOUNT | FLOAT | The amount of the second token added or removed from the pool, adjusted for decimals | | LIQUIDITY\_POOL\_PROTOCOL | TEXT | The liquidity pool protocol related to the action | | FACT\_LIQUIDITY\_POOL\_ACTIONS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | | \_INVOCATION\_ID | TEXT | | Was this page helpful? YesNo [Defi](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/overview) [Fact Swaps](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/fact-swaps) ⌘I --- # Aleo Data - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Aleo Aleo Data [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/overview#overview) * [Available Schemas](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/overview#available-schemas) [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/overview#overview) Overview --------------------------------------------------------------------------------------- This section contains comprehensive documentation for all Aleo data available through Flipside Crypto.[View DBT Documentation\ ----------------------\ \ View the complete technical documentation and data lineage for Aleo models](https://flipsidecrypto.github.io/aleo-models/) [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/overview#available-schemas) Available Schemas --------------------------------------------------------------------------------------------------------- [Core Tables\ -----------\ \ Tables and views in the aleo.core schema](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/overview) [Defi\ ----\ \ Tables and views in the aleo.defi schema](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/overview) [Price\ -----\ \ Tables and views in the aleo.price schema](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/overview) [Stats\ -----\ \ Tables and views in the aleo.stats schema](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/stats/overview) Was this page helpful? YesNo [Data Freshness](https://docs.flipsidecrypto.xyz/blockchain-data/data-freshness) [Core Tables](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/overview) ⌘I --- # Fact Swaps - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/fact-swaps#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Fact Swaps [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/fact-swaps#columns) **Schema**: `aleo.defi` **Table**: `fact_swaps` **Type**: Base Table Records of all swap transactions on Aleo, including both public and private swaps. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/fact-swaps#columns) Columns -------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp at which the block began. | | BLOCK\_ID | NUMBER | The block height the block was recorded at. | | TX\_ID | TEXT | The unique identifier for the transaction. | | SUCCEEDED | BOOLEAN | A boolean value indicating if the event succeeded. | | SWAPPER | TEXT | The address that initiated the swap | | FROM\_AMOUNT\_UNADJ | FLOAT | The amount of tokens input into the swap, unadjusted for decimals | | FROM\_AMOUNT | FLOAT | The amount of tokens input into the swap, adjusted for decimals | | FROM\_SYMBOL | TEXT | The token being swapped from | | FROM\_ID | TEXT | The token id being swapped from | | TO\_AMOUNT\_UNADJ | FLOAT | The amount of tokens received from the swap, unadjusted for decimals | | TO\_AMOUNT | FLOAT | The amount of tokens received from the swap, adjusted for decimals | | TO\_SYMBOL | TEXT | The token being swapped to | | TO\_ID | TEXT | The token id being swapped to | | ROOT\_ACTION | TEXT | The program and function that initiated the swap | | PLATFORM | TEXT | The name of the protocol where the swap occurred | | FACT\_SWAPS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | | \_INVOCATION\_ID | TEXT | | Was this page helpful? YesNo [Fact Liquidity Pool Actions](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/fact-liquidity-pool-actions) [Price](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/overview) ⌘I --- # Dim Token Registrations - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-token-registrations#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Dim Token Registrations [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-token-registrations#columns) **Schema**: `aleo.core` **Table**: `dim_token_registrations` **Type**: Base Table Dimension table containing information about token registrations on the network. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-token-registrations#columns) Columns --------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | TX\_ID\_CREATED | TEXT | Transaction ID when the token was created | | BLOCK\_ID\_CREATED | NUMBER | Block ID when the token was created | | BLOCK\_TIMESTAMP\_CREATED | TIMESTAMP\_NTZ | Block timestamp when the token was created | | TOKEN\_ID | TEXT | The ID of the token | | TOKEN\_NAME | TEXT | The decoded name of the token | | SYMBOL | TEXT | The decoded symbol of the token | | DECIMALS | NUMBER | The number of decimal places for the token | | MAX\_SUPPLY | TEXT | The maximum supply of the token | | EXTERNAL\_AUTH\_REQUIRED | BOOLEAN | Flag indicating if external authorization is required | | EXTERNAL\_AUTH\_PARTY | TEXT | The party responsible for external authorization, if required | | NAME\_ENCODED | TEXT | The original encoded name of the token | | SYMBOL\_ENCODED | TEXT | The original encoded symbol of the token | | DIM\_TOKEN\_REGISTRATIONS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | | INVOCATION\_ID | TEXT | | Was this page helpful? YesNo [Dim Programs](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-programs) [Fact Block Round Batches](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-block-round-batches) ⌘I --- # Fact Block Solutions - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-block-solutions#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Block Solutions [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-block-solutions#columns) **Schema**: `aleo.core` **Table**: `fact_block_solutions` **Type**: Base Table Records of all prover solutions for each block, including block details, rewards, and solution-specific information. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-block-solutions#columns) Columns ------------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_ID | NUMBER | The block height the block was recorded at. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp at which the block began. | | BLOCK\_PUZZLE\_REWARD | NUMBER | The total coinbase reward issued to the network for each block. | | ADDRESS | TEXT | The unique address referring to an entity on the blockchain. | | COUNTER | TEXT | A counter value associated with the solution. | | EPOCH\_HASH | TEXT | The hash of the epoch in which the solution was found. | | SOLUTION\_ID | TEXT | A unique identifier for the prover solution. | | TARGET | NUMBER | The target difficulty for the block solution. | | REWARD\_RAW | NUMBER | The raw value of the reward for solving the block. | | REWARD | FLOAT | The processed or formatted value of the reward for solving the block. | | FACT\_BLOCK\_SOLUTIONS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | | \_INVOCATION\_ID | TEXT | | Was this page helpful? YesNo [Fact Block Round Batches](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-block-round-batches) [Fact Blocks](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-blocks) ⌘I --- # Fact Block Round Batches - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-block-round-batches#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Block Round Batches [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-block-round-batches#columns) **Schema**: `aleo.core` **Table**: `fact_block_round_batches` **Type**: Base Table Records of rounds and batches within blocks on the Aleo network, capturing the consensus and block production process from genesis onward. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-block-round-batches#columns) Columns ---------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_ID | NUMBER | The block height the block was recorded at. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp at which the block began. | | ROUND | TEXT | Prover round data associated with the transaction. | | BATCH\_ID | TEXT | Batch ID associated with the transaction. | | AUTHOR | TEXT | The author of the block round. | | COMMITTEE\_ID | TEXT | The committee ID of the block round. | | TRANSMISSION\_IDS | VARIANT | The transmission IDs of the block round. | | FACT\_BLOCK\_ROUND\_BATCHES\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | | \_INVOCATION\_ID | TEXT | | Was this page helpful? YesNo [Dim Token Registrations](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-token-registrations) [Fact Block Solutions](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-block-solutions) ⌘I --- # Fact Transitions - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transitions#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Transitions [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transitions#columns) **Schema**: `aleo.core` **Table**: `fact_transitions` **Type**: Base Table Fact table containing information about all transitions within transactions on the network. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transitions#columns) Columns -------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_ID | NUMBER | The block height the block was recorded at. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp at which the block began. | | TX\_ID | TEXT | The unique identifier for the transaction. | | INDEX | NUMBER | The index of the transition within the transaction. | | TRANSITION\_ID | TEXT | The unique identifier for this specific transition within the transaction. | | SUCCEEDED | BOOLEAN | | | TYPE | TEXT | | | PROGRAM\_ID | TEXT | The identifier of the program associated with this transition. | | FUNCTION | TEXT | The function executed in this transition. | | INPUTS | VARIANT | The input parameters or data for this transition. | | OUTPUTS | VARIANT | The input parameters or data for this transition. | | FACT\_TRANSITIONS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | | \_INVOCATION\_ID | TEXT | | Was this page helpful? YesNo [Fact Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transfers) [Defi](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/overview) ⌘I --- # Fact Blocks - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-blocks#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Blocks [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-blocks#columns) **Schema**: `aleo.core` **Table**: `fact_blocks` **Type**: Base Table Records of all blocks that have occurred on the Aleo network, dating back to the genesis block. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-blocks#columns) Columns --------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_ID | NUMBER | The block height the block was recorded at. | | BLOCK\_HASH | TEXT | The hash of the block | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp at which the block began. | | NETWORK | TEXT | The network id corresponding to this block. | | TX\_COUNT | NUMBER | The number of transactions in a given block. | | PREVIOUS\_HASH | TEXT | The hash of the previous block | | ROUND | NUMBER | The round in which crpytographic proofs were provided for a given block. | | ROUNDS | ARRAY | Blocks during which provers compete to generate cryptographic proofs and solve puzzles in order to earn rewards. | | COINBASE\_TARGET | NUMBER | The coinbase target for this block | | CUMULATIVE\_PROOF\_TARGET | NUMBER | The cumulative proof target for this block | | CUMULATIVE\_WEIGHT | NUMBER | The cumulative weight for this block | | BLOCK\_REWARD | NUMBER | The total coinbase reward issued to the network for each block. | | PUZZLE\_REWARD | NUMBER | The total coinbase reward issued to the network for each block. | | FACT\_BLOCKS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | | \_INVOCATION\_ID | TEXT | | Was this page helpful? YesNo [Fact Block Solutions](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-block-solutions) [Fact Transactions](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transactions) ⌘I --- # Core Tables - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Core Tables [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/overview#overview) Overview -------------------------------------------------------------------------------------------- This schema contains 9 tables and views for Aleo data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/overview#tables-and-views) Tables and Views ------------------------------------------------------------------------------------------------------------ [Dim Labels\ ----------\ \ A hand curated table containing address names / labels for popular contracts, validators, tokens, etc.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-labels) [Dim Programs\ ------------\ \ Dimension table containing information about programs deployed on the network.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-programs) [Dim Token Registrations\ -----------------------\ \ Dimension table containing information about token registrations on the network.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-token-registrations) [Fact Block Round Batches\ ------------------------\ \ Records of rounds and batches within blocks on the Aleo network, capturing the consensus and block production process from genesis onward.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-block-round-batches) [Fact Block Solutions\ --------------------\ \ Records of all prover solutions for each block, including block details, rewards, and solution-specific information.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-block-solutions) [Fact Blocks\ -----------\ \ Records of all blocks that have occurred on the Aleo network, dating back to the genesis block.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-blocks) [Fact Transactions\ -----------------\ \ Fact table containing information about all transactions on the network.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transactions) [Fact Transfers\ --------------\ \ Records of all wallet to wallet transfers on Aleo.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transfers) [Fact Transitions\ ----------------\ \ Fact table containing information about all transitions within transactions on the network.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transitions) Was this page helpful? YesNo [Aleo Data](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/overview) [Dim Labels](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/dim-labels) ⌘I --- # Fact Transfers - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transfers#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Transfers [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transfers#columns) **Schema**: `aleo.core` **Table**: `fact_transfers` **Type**: Base Table Records of all wallet to wallet transfers on Aleo. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transfers#columns) Columns ------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_ID | NUMBER | The block height the block was recorded at. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp at which the block began. | | TX\_ID | TEXT | The unique identifier for the transaction. | | TX\_SUCCEEDED | BOOLEAN | The boolean status of the transaction. If the transaction was successful, this value will be `true`. If the transaction was unsuccessful, this value will be `false`. | | TRANSITION\_ID | TEXT | | | INDEX | NUMBER | | | TRANSFER\_TYPE | TEXT | The type of transfer, namely public or private. | | SENDER | TEXT | Address that tokens are transferred from. | | RECEIVER | TEXT | Address that tokens are transferred to. | | AMOUNT | FLOAT | Number of tokens transferred. | | IS\_NATIVE | BOOLEAN | Whether the transfer is a native transfer (credits.aleo) or a non-native transfer (token\_registry.aleo). | | TOKEN\_ADDRESS | TEXT | Token address of the transfer. | | FACT\_TRANSFERS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | | \_INVOCATION\_ID | TEXT | | Was this page helpful? YesNo [Fact Transactions](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transactions) [Fact Transitions](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transitions) ⌘I --- # Fact Transactions - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transactions#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Transactions [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transactions#columns) **Schema**: `aleo.core` **Table**: `fact_transactions` **Type**: Base Table Fact table containing information about all transactions on the network. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transactions#columns) Columns --------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_ID | NUMBER | The block height the block was recorded at. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp at which the block began. | | TX\_ID | TEXT | The unique identifier for the transaction. | | INDEX | NUMBER | The index of the transaction within the block | | TX\_SUCCEEDED | BOOLEAN | | | TX\_TYPE | TEXT | The type of the transaction (e.g., ‘execute’, ‘deploy’, ‘fee’.) | | FEE\_MSG | VARIANT | | | EXECUTION\_MSG | VARIANT | The execution message data associated with the transaction. | | DEPLOYMENT\_MSG | VARIANT | The deployment message data associated with the transaction. | | OWNER\_MSG | VARIANT | The owner message data associated with the transaction. | | FINALIZE\_MSG | VARIANT | The finalize message data associated with the transaction. | | REJECTED\_MSG | VARIANT | The rejected message data associated with the transaction. | | TRANSITION\_COUNT | NUMBER | The number of transitions in the transaction. | | FEE\_RAW | NUMBER | The raw fee value from the transaction. | | FEE | FLOAT | The native-unit fee value from the transaction. | | FACT\_TRANSACTIONS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | | \_INVOCATION\_ID | TEXT | | | FEE\_PAYER | TEXT | The account that paid the fee for the transaction. | Was this page helpful? YesNo [Fact Blocks](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-blocks) [Fact Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/core/fact-transfers) ⌘I --- # Ez Prices Hourly - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/ez-prices-hourly#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Ez Prices Hourly [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/ez-prices-hourly#columns) **Schema**: `aleo.price` **Table**: `ez_prices_hourly` **Type**: View A convenience table for determining token prices by address and blockchain, and native asset prices by symbol and blockchain. This data set is highly curated and contains metadata for one price per hour per unique asset and blockchain. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/ez-prices-hourly#columns) Columns --------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | HOUR | TIMESTAMP\_NTZ | Hour that the price was recorded at. | | TOKEN\_ADDRESS | TEXT | The specific address representing the asset on a specific platform. This will be NULL if referring to a native asset. The case (upper / lower) may or may not be specified within the `dim_asset_metadata` table, as this column is raw and not transformed, coming directly from the provider APIs. However, in the `ez_` views, it will be lowercase by default for all EVMs. | | SYMBOL | TEXT | The symbol of asset. | | NAME | TEXT | | | DECIMALS | NUMBER | The number of decimals for the asset. May be NULL. | | PRICE | FLOAT | Closing price of the recorded hour in USD. | | BLOCKCHAIN | TEXT | The Blockchain, Network, or Platform for this asset. | | IS\_NATIVE | BOOLEAN | A flag indicating assets native to the respective blockchain. | | IS\_IMPUTED | BOOLEAN | A flag indicating if the price was imputed, or derived, from the last arriving record. This is generally used for tokens with low-liquidity or inconsistent reporting. | | IS\_DEPRECATED | BOOLEAN | A flag indicating if the asset is deprecated or no longer supported by the provider. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | | EZ\_PRICES\_HOURLY\_ID | TEXT | The unique identifier for each row in the table. | Was this page helpful? YesNo [Ez Asset Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/ez-asset-metadata) [Fact Prices Ohlc Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/fact-prices-ohlc-hourly) ⌘I --- # Ez Asset Metadata - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/ez-asset-metadata#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Ez Asset Metadata [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/ez-asset-metadata#columns) **Schema**: `aleo.price` **Table**: `ez_asset_metadata` **Type**: View A convenience table holding prioritized asset metadata and other relevant details pertaining to each token\_address and native asset. This data set is highly curated and contains metadata for one unique asset per blockchain. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/ez-asset-metadata#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | TOKEN\_ADDRESS | TEXT | The specific address representing the asset on a specific platform. This will be NULL if referring to a native asset. The case (upper / lower) may or may not be specified within the `dim_asset_metadata` table, as this column is raw and not transformed, coming directly from the provider APIs. However, in the `ez_` views, it will be lowercase by default for all EVMs. | | ASSET\_ID | TEXT | The unique identifier representing the asset. | | SYMBOL | TEXT | The symbol of asset. | | NAME | TEXT | The name of asset. | | DECIMALS | NUMBER | The number of decimals for the asset. May be NULL. | | BLOCKCHAIN | TEXT | The Blockchain, Network, or Platform for this asset. | | IS\_NATIVE | BOOLEAN | A flag indicating assets native to the respective blockchain. | | IS\_DEPRECATED | BOOLEAN | A flag indicating if the asset is deprecated or no longer supported by the provider. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | | EZ\_ASSET\_METADATA\_ID | TEXT | The unique identifier for each row in the table. | Was this page helpful? YesNo [Dim Asset Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/dim-asset-metadata) [Ez Prices Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/ez-prices-hourly) ⌘I --- # Fact Prices Ohlc Hourly - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/fact-prices-ohlc-hourly#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Fact Prices Ohlc Hourly [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/fact-prices-ohlc-hourly#columns) **Schema**: `aleo.price` **Table**: `fact_prices_ohlc_hourly` **Type**: View A comprehensive fact table holding id and provider specific open, high, low, close hourly prices, from multiple providers. This data set includes raw, non-transformed data coming directly from the provider APIs and rows are not intended to be unique. As a result, there may be data quality issues persisting in the APIs that flow through to this fact based model. If you are interested in using a curated data set instead, please utilize ez\_prices\_hourly. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/fact-prices-ohlc-hourly#columns) Columns ---------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | ASSET\_ID | TEXT | The unique identifier representing the asset. | | HOUR | TIMESTAMP\_NTZ | Hour that the price was recorded at. | | OPEN | FLOAT | Opening price of the recorded hour in USD. | | HIGH | FLOAT | Highest price of the recorded hour in USD | | LOW | FLOAT | Lowest price of the recorded hour in USD | | CLOSE | FLOAT | Closing price of the recorded hour in USD | | PROVIDER | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | | FACT\_PRICES\_OHLC\_HOURLY\_ID | TEXT | The unique identifier for each row in the table. | Was this page helpful? YesNo [Ez Prices Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/ez-prices-hourly) [Stats](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/stats/overview) ⌘I --- # Ez Core Metrics Hourly - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/stats/ez-core-metrics-hourly#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Stats Ez Core Metrics Hourly [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/stats/ez-core-metrics-hourly#columns) **Schema**: `aleo.stats` **Table**: `ez_core_metrics_hourly` **Type**: Base Table Hourly core metrics for the Aleo blockchain. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/stats/ez-core-metrics-hourly#columns) Columns --------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_TIMESTAMP\_HOUR | TIMESTAMP\_NTZ | Truncated timestamp of a block. | | BLOCK\_ID\_MIN | NUMBER | Minimum block ID in an hour. | | BLOCK\_ID\_MAX | NUMBER | Maximum block ID in an hour. | | BLOCK\_COUNT | NUMBER | Number of blocks in an hour. | | TRANSACTION\_COUNT | NUMBER | Number of transactions in an hour. | | TRANSACTION\_COUNT\_SUCCESS | NUMBER | Number of successful transactions in an hour. | | TRANSACTION\_COUNT\_FAILED | NUMBER | Number of failed transactions in an hour. | | UNIQUE\_FROM\_COUNT | NUMBER | Number of unique senders in an hour. | | TOTAL\_FEES\_NATIVE | FLOAT | Total fees in native currency for an hour. | | TOTAL\_FEES\_USD | FLOAT | Total fees in USD for an hour. | | EZ\_CORE\_METRICS\_HOURLY\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | Was this page helpful? YesNo [Stats](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/stats/overview) [Aptos Data](https://docs.flipsidecrypto.xyz/blockchain-data/aptos/overview) ⌘I --- # Stats - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/stats/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Stats Stats [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/stats/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/stats/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/stats/overview#overview) Overview --------------------------------------------------------------------------------------------- This schema contains 1 tables and views for Aleo data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/stats/overview#tables-and-views) Tables and Views ------------------------------------------------------------------------------------------------------------- [Ez Core Metrics Hourly\ ----------------------\ \ Hourly core metrics for the Aleo blockchain.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/stats/ez-core-metrics-hourly) Was this page helpful? YesNo [Fact Prices Ohlc Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/fact-prices-ohlc-hourly) [Ez Core Metrics Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/stats/ez-core-metrics-hourly) ⌘I --- # Price - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Price [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/overview#overview) Overview --------------------------------------------------------------------------------------------- This schema contains 4 tables and views for Aleo data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/overview#tables-and-views) Tables and Views ------------------------------------------------------------------------------------------------------------- [Dim Asset Metadata\ ------------------\ \ A comprehensive dimensional table holding asset metadata and other relevant details pertaining to each id, from multiple providers.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/dim-asset-metadata) [Ez Asset Metadata\ -----------------\ \ A convenience table holding prioritized asset metadata and other relevant details pertaining to each token\_address and native asset.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/ez-asset-metadata) [Ez Prices Hourly\ ----------------\ \ A convenience table for determining token prices by address and blockchain, and native asset prices by symbol and blockchain.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/ez-prices-hourly) [Fact Prices Ohlc Hourly\ -----------------------\ \ A comprehensive fact table holding id and provider specific open, high, low, close hourly prices, from multiple providers.](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/fact-prices-ohlc-hourly) Was this page helpful? YesNo [Fact Swaps](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/defi/fact-swaps) [Dim Asset Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/aleo/price/dim-asset-metadata) ⌘I --- # Ez Lending Ohlc Rates - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/defi/ez-lending-ohlc-rates#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Ez Lending Ohlc Rates [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/defi/ez-lending-ohlc-rates#columns) **Schema**: `ethereum.defi` **Table**: `ez_lending_ohlc_rates` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/defi/ez-lending-ohlc-rates#columns) Columns ----------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | DAY | TIMESTAMP\_NTZ | | | PROTOCOL | TEXT | | | PLATFORM | TEXT | | | VERSION | TEXT | | | TOKEN\_ADDRESS | TEXT | | | TOKEN\_SYMBOL | TEXT | | | SUPPLY\_RATE\_OPEN | FLOAT | | | SUPPLY\_RATE\_HIGH | FLOAT | | | SUPPLY\_RATE\_LOW | FLOAT | | | SUPPLY\_RATE\_CLOSE | FLOAT | | | STABLE\_BORROW\_RATE\_OPEN | FLOAT | | | STABLE\_BORROW\_RATE\_HIGH | FLOAT | | | STABLE\_BORROW\_RATE\_LOW | FLOAT | | | STABLE\_BORROW\_RATE\_CLOSE | FLOAT | | | VARIABLE\_BORROW\_RATE\_OPEN | FLOAT | | | VARIABLE\_BORROW\_RATE\_HIGH | FLOAT | | | VARIABLE\_BORROW\_RATE\_LOW | FLOAT | | | VARIABLE\_BORROW\_RATE\_CLOSE | FLOAT | | | RATE\_UPDATES\_COUNT | NUMBER | | | BLOCKCHAIN | TEXT | | | EZ\_OHLC\_RATES\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | Was this page helpful? YesNo [Ez Lending Liquidations](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/defi/ez-lending-liquidations) [Ez Lending Repayments](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/defi/ez-lending-repayments) ⌘I --- # Fact Vat File - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-file#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Maker Fact Vat File [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-file#columns) **Schema**: `ethereum.maker` **Table**: `fact_vat_file` **Type**: View Admin function to modify the system parameters. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-file#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | CONTRACT_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: - Always the immediate event emitter for logs - May differ from transaction to_address - Lowercase normalized format - Never NULL for valid events | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ILK | TEXT | The collateral type of the CDP. | | WHAT | TEXT | | | DATA | TEXT | | | FACT\_VAT\_FILE\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Fact Urns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-urns) [Fact Vat Flux](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-flux) ⌘I --- # Fact Vat Flux - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-flux#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Maker Fact Vat Flux [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-flux#columns) **Schema**: `ethereum.maker` **Table**: `fact_vat_flux` **Type**: View Transfers of internal collateral balance of collateral type ilk within Vat from src to dst address. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-flux#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | CONTRACT_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: - Always the immediate event emitter for logs - May differ from transaction to_address - Lowercase normalized format - Never NULL for valid events | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ILK | TEXT | The collateral type of the CDP. | | RECEIVER | TEXT | | | SENDER | TEXT | | | WAD | FLOAT | | | FACT\_VAT\_FLUX\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Fact Vat File](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-file) [Fact Vat Fold](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-fold) ⌘I --- # Fact Vat Fold - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-fold#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Maker Fact Vat Fold [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-fold#columns) **Schema**: `ethereum.maker` **Table**: `fact_vat_fold` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-fold#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | CONTRACT_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: - Always the immediate event emitter for logs - May differ from transaction to_address - Lowercase normalized format - Never NULL for valid events | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ILK | TEXT | The collateral type of the CDP. | | U | TEXT | | | RATE | FLOAT | Stablecoin debt multiplier (accumulated stability fees) | | FACT\_VAT\_FOLD\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Fact Vat Flux](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-flux) [Fact Vat Fork](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-fork) ⌘I --- # Fact Vat Fork - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-fork#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Maker Fact Vat Fork [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-fork#columns) **Schema**: `ethereum.maker` **Table**: `fact_vat_fork` **Type**: View Moves locked collateral and/or outstanding debt from one vault src to another vault dst by dink and dart amounts. This is a public function that can be called by an address that is authorized by both src and dst vaults. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-fork#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | CONTRACT_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: - Always the immediate event emitter for logs - May differ from transaction to_address - Lowercase normalized format - Never NULL for valid events | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ILK | TEXT | The collateral type of the CDP. | | SRC | TEXT | | | DST | TEXT | | | DINK | FLOAT | Amount of collateral to exchange. | | DART | FLOAT | Amount of stablecoin debt to exchange. | | FACT\_VAT\_FORK\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Fact Vat Fold](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-fold) [Fact Vat Frob](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-frob) ⌘I --- # Fact Vat Frob - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-frob#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Maker Fact Vat Frob [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-frob#columns) **Schema**: `ethereum.maker` **Table**: `fact_vat_frob` **Type**: View Manipulates the locked collateral and outstanding debt balance of a vault u with collateral balance from address v and dai balance of address w Positive dink and dart values add to the existing balances while negative value subtract from them. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-frob#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | CONTRACT_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: - Always the immediate event emitter for logs - May differ from transaction to_address - Lowercase normalized format - Never NULL for valid events | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ILK | TEXT | The collateral type of the CDP. | | U\_ADDRESS | TEXT | | | V\_ADDRESS | TEXT | | | W\_ADDRESS | TEXT | | | DINK | FLOAT | Change in collateral. | | DART | FLOAT | Change in debt. | | FACT\_VAT\_FROB\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Fact Vat Fork](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-fork) [Fact Vat Move](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-move) ⌘I --- # Fact Vat Slip - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-slip#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Maker Fact Vat Slip [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-slip#columns) **Schema**: `ethereum.maker` **Table**: `fact_vat_slip` **Type**: View Used to modify the internal collateral balance of a collateral type within Vat. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-slip#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | CONTRACT_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: - Always the immediate event emitter for logs - May differ from transaction to_address - Lowercase normalized format - Never NULL for valid events | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ILK | TEXT | The collateral type of the CDP. | | USR | TEXT | | | WAD | FLOAT | | | FACT\_VAT\_SLIP\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Fact Vat Move](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-move) [Fact Vat Suck](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-suck) ⌘I --- # Fact Vat Move - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-move#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Maker Fact Vat Move [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-move#columns) **Schema**: `ethereum.maker` **Table**: `fact_vat_move` **Type**: View Used to transfer internal dai balance of user within Vat to another address. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-move#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | CONTRACT_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: - Always the immediate event emitter for logs - May differ from transaction to_address - Lowercase normalized format - Never NULL for valid events | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | SRC\_ADDRESS | TEXT | | | DST\_ADDRESS | TEXT | | | RAD | FLOAT | DAI amount. | | FACT\_VAT\_MOVE\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Fact Vat Frob](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-frob) [Fact Vat Slip](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-slip) ⌘I --- # Fact Vat Suck - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-suck#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Maker Fact Vat Suck [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-suck#columns) **Schema**: `ethereum.maker` **Table**: `fact_vat_suck` **Type**: View Generates dai on address u and accounted as bad debt on address v without opening a vault. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-suck#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | CONTRACT_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: - Always the immediate event emitter for logs - May differ from transaction to_address - Lowercase normalized format - Never NULL for valid events | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | U\_ADDRESS | TEXT | | | V\_ADDRESS | TEXT | | | RAD | FLOAT | | | FACT\_VAT\_SUCK\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Fact Vat Slip](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-slip) [Nft](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/overview) ⌘I --- # Dim Nft Collection Metadata - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/dim-nft-collection-metadata#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Dim Nft Collection Metadata [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/dim-nft-collection-metadata#columns) **Schema**: `ethereum.nft` **Table**: `dim_nft_collection_metadata` **Type**: View This table contains the metadata for popular NFT collections on the Ethereum blockchain. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/dim-nft-collection-metadata#columns) Columns ---------------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCKCHAIN | TEXT | Blockchain where the NFT metadata is retrieved from. | | CONTRACT\_ADDRESS | TEXT | The smart contract address of the NFT collection. Supports ERC-721, ERC-1155, and custom implementations. | Example: ‘0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d’ | | COLLECTION\_NAME | TEXT | The name for this NFT collection. | | TOKEN\_ID | TEXT | The unique identifier of the specific NFT within its collection. Format is numeric string. Example: ‘1234’ | | TRAITS | VARIANT | The traits for this tokenId in a key-value pair format. | | TOKEN\_ID\_NAME | TEXT | The name for this specific tokenId. This may be the same for all tokenIds within the same collection. | | TOKEN\_ID\_DESCRIPTION | TEXT | The description for this specific tokenId. This may be the same for all tokenIds within the same collection. | | TOKEN\_ID\_IMAGE\_URL | TEXT | The url of the image for this tokenId. | | NFT\_ADDRESS\_TOKEN\_ID | TEXT | The concatenation of nft address and tokenId. | | DIM\_NFT\_COLLECTION\_METADATA\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Nft](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/overview) [Ez Lending Liquidations](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-liquidations) ⌘I --- # Ez Lending Loans - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-loans#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Ez Lending Loans [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-loans#columns) **Schema**: `ethereum.nft` **Table**: `ez_lending_loans` **Type**: View This table contains NFT lending events for loans backed by collateralized NFTs on Ethereum. For Blur’s Blend, this could be depositing an NFT and taking out a loan or using the Buy Now Pay Later (BNPL) feature to take a loan out of the newly bought NFT. This NFT will remain locked until the loan is cleared. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-loans#columns) Columns ----------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | EVENT_TYPE | TEXT | There are 2 types of loan creation events. It can either be a new loan or a refinance of an existing loan. Note that for NFTfi, renegotiation events are categorised as refinance events in this table. As for the refinancing feature on NFTfi, old loans are repaid and new loan ids are reissued so these would be new loan entries in this table. | | PLATFORM_NAME | TEXT | The name of the platform | | PLATFORM_ADDRESS | TEXT | The contract address of the platform's lending contract | | PLATFORM_EXCHANGE_VERSION | TEXT | The version of the platform's lending contract | | LOAN_ID | TEXT | The ID associated with the loan, often times tied to the borrower's address and collateral. For the case of Blur's blend, this ID can be used as a unique identifier when tracking active loans. However, note that refinances can happen while still maintaining the same loanId. For platforms like NFTFI, loanids of previously paid loans are reused hence they can't be reliably used as a unique identifier without appropriate timestamp filters. Instead, use the unique_loan_id column. | | UNIQUE_LOAN_ID | TEXT | The unique ID that can be used to represent a loan within the same platform. For the same loan, the value of this ID will remain the same across the loans taken, liquidations and repayment tables. For some platforms like NFTFI where the lender is issued a promissory note, the lender can send this note to any address, making the receiver the new lender. However, the unique_loan_id still remains the same although the final lender is different. For Blend, unique_loan_id changes only if the loanId and lender changes which would also indicate the previous loan has been fully paid off. | | LENDER_ADDRESS | TEXT | The address that gives out a loan to the borrower. In the case of NFTFI, when a loan is issued, a promissory note (an ERC721) is issued to the lender. The lender can transfer this note to any address which makes any receiving address the new "lender" | | BORROWER_ADDRESS | TEXT | The address that receives the loan and has an NFT locked as collateral | | NAME | TEXT | The name of the NFT collection or project. May be NULL for unverified collections. Example: 'Bored Ape Yacht Club' | | CONTRACT_ADDRESS | TEXT | The address of the NFT used as collateral | | TOKEN_ID | TEXT | The tokenId of the NFT used as collateral | | LOAN_TOKEN_ADDRESS | TEXT | The contract address of what the loan is denominated in. For Blend, this is Blur's ETH while for NFTFI this could be either WETH, DAI or USDC | | LOAN_TOKEN_SYMBOL | TEXT | The symbol of the loan token address. For Blur Pool, the symbol is ETH | | PRINCIPAL_UNADJ | NUMBER | The principal amount of the loan taken with unadjusted decimal places | | PRINCIPAL | FLOAT | The principal amount of the loan taken with adjusted decimal places | | PRINCIPAL_USD | FLOAT | The principal amount of the loan taken in USD terms | | DEBT_UNADJ | NUMBER | The total debt of the loan (principal amount plus interests) with unadjusted decimal places | | DEBT | FLOAT | The total debt of the loan (principal amount plus interests) with adjusted decimal places | | DEBT_USD | FLOAT | The total debt of the loan (principal amount plus interests) in USD terms | | PLATFORM_FEE_UNADJ | FLOAT | The fee charged by the lending platform with unadjusted decimal places | | PLATFORM_FEE | FLOAT | The fee charged by the lending platform with adjusted decimal places | | PLATFORM_FEE_USD | FLOAT | The fee charged by the lending platform in USD terms | | INTEREST_RATE | FLOAT | The non-annualized rate charged by the lender on the principal amount of the loan denominated in percentage (%). For fixed term loans, it is calculated by taking the difference between total debt and principal amount divided by principal amount. For perpetual term loans, interest rate is usually on an annual basis and total debt is calculated prorated | | APR | FLOAT | The annualized interest rate denominated in percentage (%). | | LOAN_TERM_TYPE | TEXT | The type of loan terms, could be either a fixed loan or a perpetual loan. A fixed term loan as a fixed repayment date while a perpetual loan does not. | | LOAN_START_TIMESTAMP | TIMESTAMP_NTZ | The timestamp of when the loan offer is accepted | | LOAN_DUE_TIMESTAMP | TIMESTAMP_NTZ | The timestamp of when the loan is due. For perpetual term loan, the value will be null | | LOAN_TENURE | NUMBER | The tenure of the loan denominated in seconds. For perpetual term loan, the value will be null | | TX_FEE | FLOAT | Total fee paid for transaction execution in native token units. Example: 0.002 | | TX_FEE_USD | FLOAT | The transaction fee in USD terms | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: * 0xa9059cbb: transfer(address,uint256) * 0x095ea7b3: approve(address,uint256) * 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | EZ\_NFT\_LENDING\_LOANS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Lending Liquidations](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-liquidations) [Ez Lending Repayments](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-repayments) ⌘I --- # Ez Lending Liquidations - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-liquidations#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Ez Lending Liquidations [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-liquidations#columns) **Schema**: `ethereum.nft` **Table**: `ez_lending_liquidations` **Type**: View This table contains liquidation events for loans backed by collateralized NFTs on Ethereum. This typically means the lender of the loan closes the loan and receives the NFT collateral [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-liquidations#columns) Columns ------------------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | PLATFORM_NAME | TEXT | The name of the platform | | PLATFORM_ADDRESS | TEXT | The contract address of the platform's lending contract | | PLATFORM_EXCHANGE_VERSION | TEXT | The version of the platform's lending contract | | LOAN_ID | TEXT | The ID associated with the loan, often times tied to the borrower's address and collateral. For the case of Blur's blend, this ID can be used as a unique identifier when tracking active loans. However, note that refinances can happen while still maintaining the same loanId. For platforms like NFTFI, loanids of previously paid loans are reused hence they can't be reliably used as a unique identifier without appropriate timestamp filters. Instead, use the unique_loan_id column. | | UNIQUE_LOAN_ID | TEXT | The unique ID that can be used to represent a loan within the same platform. For the same loan, the value of this ID will remain the same across the loans taken, liquidations and repayment tables. For some platforms like NFTFI where the lender is issued a promissory note, the lender can send this note to any address, making the receiver the new lender. However, the unique_loan_id still remains the same although the final lender is different. For Blend, unique_loan_id changes only if the loanId and lender changes which would also indicate the previous loan has been fully paid off. | | LENDER_ADDRESS | TEXT | The address that gives out a loan to the borrower. In the case of NFTFI, when a loan is issued, a promissory note (an ERC721) is issued to the lender. The lender can transfer this note to any address which makes any receiving address the new "lender" | | BORROWER_ADDRESS | TEXT | The address that receives the loan and has an NFT locked as collateral | | NAME | TEXT | The name of the NFT collection or project. May be NULL for unverified collections. Example: 'Bored Ape Yacht Club' | | CONTRACT_ADDRESS | TEXT | The address of the NFT used as collateral | | TOKEN_ID | TEXT | The tokenId of the NFT used as collateral | | LOAN_TOKEN_ADDRESS | TEXT | The contract address of what the loan is denominated in. For Blend, this is Blur's ETH while for NFTFI this could be either WETH, DAI or USDC | | LOAN_TOKEN_SYMBOL | TEXT | The symbol of the loan token address. For Blur Pool, the symbol is ETH | | PRINCIPAL_UNADJ | NUMBER | The principal amount of the loan taken with unadjusted decimal places | | PRINCIPAL | FLOAT | The principal amount of the loan taken with adjusted decimal places | | PRINCIPAL_USD | FLOAT | The principal amount of the loan taken in USD terms | | INTEREST_RATE | FLOAT | The non-annualized rate charged by the lender on the principal amount of the loan denominated in percentage (%). For fixed term loans, it is calculated by taking the difference between total debt and principal amount divided by principal amount. For perpetual term loans, interest rate is usually on an annual basis and total debt is calculated prorated | | APR | FLOAT | The annualized interest rate denominated in percentage (%). | | LOAN_TERM_TYPE | TEXT | The type of loan terms, could be either a fixed loan or a perpetual loan. A fixed term loan as a fixed repayment date while a perpetual loan does not. | | LOAN_START_TIMESTAMP | TIMESTAMP_NTZ | The timestamp of when the loan offer is accepted | | LOAN_DUE_TIMESTAMP | TIMESTAMP_NTZ | The timestamp of when the loan is due. For perpetual term loan, the value will be null | | TX_FEE | FLOAT | Total fee paid for transaction execution in native token units. Example: 0.002 | | TX_FEE_USD | FLOAT | The transaction fee in USD terms | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: * 0xa9059cbb: transfer(address,uint256) * 0x095ea7b3: approve(address,uint256) * 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | EZ\_NFT\_LENDING\_LIQUIDATIONS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Dim Nft Collection Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/dim-nft-collection-metadata) [Ez Lending Loans](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-loans) ⌘I --- # Maker - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Maker Maker [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/overview#overview) Overview ------------------------------------------------------------------------------------------------- This schema contains 20 tables and views for Ethereum data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/overview#tables-and-views) Tables and Views ----------------------------------------------------------------------------------------------------------------- [Fact Cat Bite\ -------------\ \ The Cat is the system’s liquidation agent: it enables keepers to mark positions as unsafe and send them to be auctioned.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-cat-bite) [Fact Cdp Flux\ -------------\ \ Wad amounts of CDP collateral from the cdp address to a dst address.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-cdp-flux) [Fact Cdp Frob\ -------------\ \ Modifications of the collateral and debt balance of a CDP.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-cdp-frob) [Fact Cdp Move\ -------------\ \ Transfers of DAI from the cdp address to a dst address.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-cdp-move) [Fact Cdp Newcdp\ ---------------\ \ Creates a new CDP.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-cdp-newcdp) [Fact Dai Join Exit\ ------------------\ \ Removes collateral into the system.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-dai-join-exit) [Fact Dai Join Join\ ------------------\ \ Enters collateral into the system.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-dai-join-join) [Fact Dog Bark\ -------------\ \ This is the v1 liquidation function.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-dog-bark) [Fact Dss Flashloan\ ------------------\ \ This table tracks flash loan events from MakerDAO’s DssFlash module, capturing uncollateralized borrows and repayments.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-dss-flashloan) [Fact Pot Exit\ -------------\ \ Used when users want to “exit” their Dai from the Pot.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-pot-exit) [Fact Pot Join\ -------------\ \ Used when users want to join their Dai to the Pot.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-pot-join) [Fact Urns\ ---------\ \ Urn addresses are read by calling the urns function on the CDP manager contract for each created vault.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-urns) [Fact Vat File\ -------------\ \ Admin function to modify the system parameters.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-file) [Fact Vat Flux\ -------------\ \ Transfers of internal collateral balance of collateral type ilk within Vat from src to dst address.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-flux) [Fact Vat Fold\ -------------\ \ This table contains records of stability fee accrual events, tracking interest rate accumulation on outstanding debt positions.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-fold) [Fact Vat Fork\ -------------\ \ Moves locked collateral and/or outstanding debt from one vault src to another vault dst by dink and dart amounts.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-fork) [Fact Vat Frob\ -------------\ \ Manipulates the locked collateral and outstanding debt balance of a vault u with collateral balance from address v and dai balance of address w Pos…](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-frob) [Fact Vat Move\ -------------\ \ Used to transfer internal dai balance of user within Vat to another address.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-move) [Fact Vat Slip\ -------------\ \ Used to modify the internal collateral balance of a collateral type within Vat.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-slip) [Fact Vat Suck\ -------------\ \ Generates dai on address u and accounted as bad debt on address v without opening a vault.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-suck) Was this page helpful? YesNo [Ez State Validation](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/l2/ez-state-validation) [Fact Cat Bite](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-cat-bite) ⌘I --- # Ez Mev Arbitrage - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-mev-arbitrage#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Ez Mev Arbitrage [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-mev-arbitrage#columns) **Schema**: `ethereum.nft` **Table**: `ez_mev_arbitrage` **Type**: View This table contains the financial metrics from NFT arbitrage transactions including cost, revenue and profits. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-mev-arbitrage#columns) Columns ----------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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\_SEARCHER | TEXT | The address of the MEV finder, taken from the origin address that initiated the transaction | | MEV\_CONTRACT | TEXT | The contract address that the MEV searcher uses to execute mev transactions, taken from the origin to address of the transaction | | COST\_USD | FLOAT | The total cost in USD to purchase the NFT(s) in the transaction | | REVENUE\_USD | FLOAT | The total revenue in USD from selling the NFT(s) and other related tokens in the transaction | | MINER\_TIP\_USD | FLOAT | The total amount in USD sent to the block miner/builder as a tip to include the transaction in the block | | TX\_FEE\_USD | FLOAT | The transaction fee in USD terms | | PROFIT\_USD | FLOAT | The remainder in USD after subtracting cost, miner tip and transaction fee from revenue | | FUNDING\_SOURCE | TEXT | The 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\_DIRECTION | TEXT | The 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\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Lending Repayments](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-repayments) [Ez Nft Sales](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales) ⌘I --- # Ez Lending Repayments - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-repayments#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Ez Lending Repayments [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-repayments#columns) **Schema**: `ethereum.nft` **Table**: `ez_lending_repayments` **Type**: View This table contains repayment events for loans backed by collateralized NFTs on Ethereum. Events in this table can be a full repayment either by the borrower to get their collateral back or by a new lender to repay the borrower’s previous loan. The latter is labeled as ‘refinance’ where the same borrower takes on a new loan from a new lender and repays the past loan. The NFT collateral is still locked in this scenario. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-repayments#columns) Columns ---------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | EVENT_TYPE | TEXT | There are 2 types of loan repayment events. It can either be repay or refinance. 'repay' events are full repayment events by the borrower to get their collateral back while 'refinance' events represent the same borrower engaging a new lender and repay their past loan. The collateral is still locked in this scenario. | | PLATFORM_NAME | TEXT | The name of the platform | | PLATFORM_ADDRESS | TEXT | The contract address of the platform's lending contract | | PLATFORM_EXCHANGE_VERSION | TEXT | The version of the platform's lending contract | | LOAN_ID | TEXT | The ID associated with the loan, often times tied to the borrower's address and collateral. For the case of Blur's blend, this ID can be used as a unique identifier when tracking active loans. However, note that refinances can happen while still maintaining the same loanId. For platforms like NFTFI, loanids of previously paid loans are reused hence they can't be reliably used as a unique identifier without appropriate timestamp filters. Instead, use the unique_loan_id column. | | UNIQUE_LOAN_ID | TEXT | The unique ID that can be used to represent a loan within the same platform. For the same loan, the value of this ID will remain the same across the loans taken, liquidations and repayment tables. For some platforms like NFTFI where the lender is issued a promissory note, the lender can send this note to any address, making the receiver the new lender. However, the unique_loan_id still remains the same although the final lender is different. For Blend, unique_loan_id changes only if the loanId and lender changes which would also indicate the previous loan has been fully paid off. | | LENDER_ADDRESS | TEXT | The address that gives out a loan to the borrower. In the case of NFTFI, when a loan is issued, a promissory note (an ERC721) is issued to the lender. The lender can transfer this note to any address which makes any receiving address the new "lender" | | BORROWER_ADDRESS | TEXT | The address that receives the loan and has an NFT locked as collateral | | NAME | TEXT | The name of the NFT collection or project. May be NULL for unverified collections. Example: 'Bored Ape Yacht Club' | | CONTRACT_ADDRESS | TEXT | The address of the NFT used as collateral | | TOKEN_ID | TEXT | The tokenId of the NFT used as collateral | | LOAN_TOKEN_ADDRESS | TEXT | The contract address of what the loan is denominated in. For Blend, this is Blur's ETH while for NFTFI this could be either WETH, DAI or USDC | | LOAN_TOKEN_SYMBOL | TEXT | The symbol of the loan token address. For Blur Pool, the symbol is ETH | | PRINCIPAL_UNADJ | NUMBER | The principal amount of the loan taken with unadjusted decimal places | | PRINCIPAL | FLOAT | The principal amount of the loan taken with adjusted decimal places | | PRINCIPAL_USD | FLOAT | The principal amount of the loan taken in USD terms | | DEBT_UNADJ | FLOAT | The total debt of the loan (principal amount plus interests) with unadjusted decimal places | | DEBT | FLOAT | The total debt of the loan (principal amount plus interests) with adjusted decimal places | | DEBT_USD | FLOAT | The total debt of the loan (principal amount plus interests) in USD terms | | PLATFORM_FEE_UNADJ | FLOAT | The fee charged by the lending platform with unadjusted decimal places | | PLATFORM_FEE | FLOAT | The fee charged by the lending platform with adjusted decimal places | | PLATFORM_FEE_USD | FLOAT | The fee charged by the lending platform in USD terms | | INTEREST_RATE | FLOAT | The non-annualized rate charged by the lender on the principal amount of the loan denominated in percentage (%). For fixed term loans, it is calculated by taking the difference between total debt and principal amount divided by principal amount. For perpetual term loans, interest rate is usually on an annual basis and total debt is calculated prorated | | APR | FLOAT | The annualized interest rate denominated in percentage (%). | | LOAN_TERM_TYPE | TEXT | The type of loan terms, could be either a fixed loan or a perpetual loan. A fixed term loan as a fixed repayment date while a perpetual loan does not. | | LOAN_START_TIMESTAMP | TIMESTAMP_NTZ | The timestamp of when the loan offer is accepted | | LOAN_DUE_TIMESTAMP | TIMESTAMP_NTZ | The timestamp of when the loan is due. For perpetual term loan, the value will be null | | LOAN_PAID_TIMESTAMP | TIMESTAMP_NTZ | The timestamp of when the loan is fully paid off. | | TX_FEE | FLOAT | Total fee paid for transaction execution in native token units. Example: 0.002 | | TX_FEE_USD | FLOAT | The transaction fee in USD terms | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: * 0xa9059cbb: transfer(address,uint256) * 0x095ea7b3: approve(address,uint256) * 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | EZ\_NFT\_LENDING\_REPAYMENTS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Lending Loans](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-loans) [Ez Mev Arbitrage](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-mev-arbitrage) ⌘I --- # Ez Nft Sales - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Ez Nft Sales [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales#commonly-used-fields) * [Sample Queries](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales#columns) **Schema**: `ethereum.nft` **Table**: `ez_nft_sales` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales#what) What ------------------------------------------------------------------------------------------- This table provides a comprehensive view of NFT (Non-Fungible Token) sales across all major marketplaces and platforms on EVM blockchains. It captures both direct marketplace sales and aggregator-routed transactions, enabling analysis of NFT market dynamics, collection performance, and trading patterns. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------- * Analyze daily/weekly NFT market volume and trends by platform * Track top-performing NFT collections by sales count and volume * Monitor marketplace competition and market share analysis * Identify whale activity and buyer behavior patterns * Evaluate creator royalty enforcement across platforms * Assess fee structures and revenue models by marketplace * Track cross-platform trader behavior and platform preferences [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales#important-relationships) Important Relationships --------------------------------------------------------------------------------------------------------------------------------- * Links to `core.fact_event_logs` via `tx_hash` and `event_index` * Joins with `core.dim_contracts` for collection name * References `price.ez_prices_hourly` for currency conversions * Connects to token transfer tables for ownership tracking [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales#commonly-used-fields) Commonly-used Fields --------------------------------------------------------------------------------------------------------------------------- * `platform_name`: Marketplace where sale occurred (opensea, blur, etc.) * `contract_address`: NFT collection contract address * `token_id`: Unique identifier of the specific NFT * `buyer_address` / `seller_address`: Transaction participants * `price_usd`: Sale price converted to USD (includes fees) * `total_fees_usd`: Combined platform and creator fees in USD * `event_type`: Type of sale transaction (sale, bid\_won, etc.) [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales#sample-queries) Sample Queries --------------------------------------------------------------------------------------------------------------- **Daily NFT market volume by platform** Copy Ask AI -- Daily NFT market volume by platform SELECT DATE_TRUNC('day', block_timestamp) AS date, platform_name, COUNT(*) as sales_count, COUNT(DISTINCT tx_hash) AS unique_sales_transaction_count, COUNT(DISTINCT buyer_address) AS unique_buyers, COUNT(DISTINCT contract_address) AS collections_traded, SUM(price_usd) AS total_volume_usd, AVG(price_usd) AS avg_sale_price_usd FROM .nft.ez_nft_sales WHERE block_timestamp >= CURRENT_DATE - 30 AND price_usd IS NOT NULL GROUP BY 1, 2 ORDER BY 1 DESC, 7 DESC; **Top selling NFT collections** Copy Ask AI -- Top selling NFT collections SELECT contract_address, name AS collection_name, COUNT(*) AS sales_count, COUNT(DISTINCT token_id) AS unique_tokens_sold, COUNT(DISTINCT buyer_address) AS unique_buyers, SUM(price_usd) AS total_volume_usd, AVG(price_usd) AS avg_price_usd, MAX(price_usd) AS highest_sale_usd FROM .nft.ez_nft_sales WHERE block_timestamp >= CURRENT_DATE - 7 AND price_usd IS NOT NULL GROUP BY 1, 2 ORDER BY 6 DESC LIMIT 50; **Marketplace competition analysis** Copy Ask AI -- Marketplace competition analysis WITH platform_metrics AS ( SELECT platform_name, COUNT(*) AS total_sales, SUM(price_usd) AS total_volume_usd, COUNT(DISTINCT buyer_address) AS unique_buyers, COUNT(DISTINCT seller_address) AS unique_sellers, AVG(platform_fee / NULLIF(price, 0) * 100) AS avg_platform_fee_pct, SUM(platform_fee_usd) AS total_platform_revenue_usd FROM .nft.ez_nft_sales WHERE block_timestamp >= CURRENT_DATE - 30 AND price_usd IS NOT NULL GROUP BY 1 ) SELECT platform_name, total_sales, total_volume_usd, total_volume_usd * 100.0 / SUM(total_volume_usd) OVER () AS market_share_pct, unique_buyers, unique_sellers, avg_platform_fee_pct, total_platform_revenue_usd FROM platform_metrics ORDER BY total_volume_usd DESC; **Whale activity tracking** Copy Ask AI -- Whale activity tracking WITH buyer_stats AS ( SELECT buyer_address, COUNT(*) AS purchases, COUNT(DISTINCT contract_address) AS unique_collections, SUM(price_usd) AS total_spent_usd, AVG(price_usd) AS avg_purchase_price, MAX(price_usd) AS highest_purchase FROM .nft.ez_nft_sales WHERE block_timestamp >= CURRENT_DATE - 30 AND price_usd IS NOT NULL GROUP BY 1 ) SELECT CASE WHEN total_spent_usd < 1000 THEN '< $1K' WHEN total_spent_usd < 10000 THEN '$1K - $10K' WHEN total_spent_usd < 100000 THEN '$10K - $100K' WHEN total_spent_usd < 1000000 THEN '$100K - $1M' ELSE '> $1M' END AS buyer_tier, COUNT(*) AS buyer_count, SUM(purchases) AS total_purchases, AVG(unique_collections) AS avg_collections_per_buyer, SUM(total_spent_usd) AS tier_total_spent FROM buyer_stats GROUP BY 1 ORDER BY MIN(total_spent_usd); **Creator royalty analysis** Copy Ask AI -- Creator royalty analysis SELECT name AS collection_name, contract_address, COUNT(*) AS sales_with_royalties, SUM(creator_fee) AS total_creator_fees, SUM(creator_fee_usd) AS total_creator_fees_usd, AVG(creator_fee / NULLIF(price, 0) * 100) AS avg_royalty_pct, SUM(creator_fee_usd) / NULLIF(SUM(price_usd), 0) * 100 AS effective_royalty_rate FROM .nft.ez_nft_sales WHERE creator_fee > 0 AND price > 0 AND block_timestamp >= CURRENT_DATE - 30 GROUP BY 1, 2 HAVING COUNT(*) > 10 ORDER BY total_creator_fees_usd DESC LIMIT 100; [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales#columns) Columns ------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | FLOAT | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | EVENT_TYPE | TEXT | The specific type of NFT transaction that occurred. Common values include 'sale', 'bid_won', 'redeem', and 'mint'. Example: 'sale' | | PLATFORM_ADDRESS | TEXT | The smart contract address of the marketplace facilitating the sale. Platforms may have multiple contracts for different versions. Example: '0x00000000006c3852cbef3e08e8df289169ede581' | | PLATFORM_NAME | TEXT | The marketplace or platform where the NFT sale occurred. Standardized to lowercase with no spaces. Example: 'opensea' | | PLATFORM_EXCHANGE_VERSION | TEXT | The version identifier of the marketplace contract. Tracks protocol versions and upgrades. Example: 'seaport_1_5' | | AGGREGATOR_NAME | TEXT | The NFT aggregator platform that routed the transaction. NULL indicates direct platform interaction. Example: 'gem' | | SELLER_ADDRESS | TEXT | The blockchain address that sold the NFT. Example: '0x1234567890123456789012345678901234567890' | | BUYER_ADDRESS | TEXT | The blockchain address that purchased the NFT. Example: '0x1234567890123456789012345678901234567890' | | CONTRACT_ADDRESS | TEXT | The smart contract address of the NFT collection. Supports ERC-721, ERC-1155, and custom implementations. Example: '0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d' | | NAME | TEXT | The name of the NFT collection or project. May be NULL for unverified collections. Example: 'Bored Ape Yacht Club' | | TOKEN_ID | TEXT | The unique identifier of the specific NFT within its collection. Format is numeric string. Example: '1234' | | QUANTITY | TEXT | The number of tokens sold in the transaction. Primarily relevant for ERC-1155 tokens. Example: '1' | | TOKEN_STANDARD | TEXT | The technical standard implemented by the NFT contract. Common values include 'erc721', 'erc1155', 'cryptopunks', and 'legacy'. Example: 'erc721' | | CURRENCY_SYMBOL | TEXT | The symbol of the token used for payment. Example: 'ETH' | | CURRENCY_ADDRESS | TEXT | The contract address of the payment token. Shows 'ETH' for native ETH payments. Example: '0xa0b86a33e6776a1e7f9f0b8b8b8b8b8b8b8b8b8b' | | PRICE | FLOAT | The sale price in the payment currency, including platform and creator fees. Raw price before USD conversion. Example: 2.5 | | PRICE_USD | FLOAT | The sale price converted to USD at transaction time, including platform and creator fees. May be NULL for missing price data. Example: 4250.75 | | TOTAL_FEES | FLOAT | The combined platform and creator fees in the payment currency. Example: 0.125 | | PLATFORM_FEE | FLOAT | The fee charged by the marketplace in the payment currency. Typically 2-2.5% of sale price. Example: 0.05 | | CREATOR_FEE | FLOAT | The royalty fee paid to the collection creator in the payment currency. Typically 0-10% of sale price. Example: 0.075 | | TOTAL_FEES_USD | FLOAT | The combined platform and creator fees converted to USD. Example: 212.54 | | PLATFORM_FEE_USD | FLOAT | The marketplace fee converted to USD. Example: 85.02 | | CREATOR_FEE_USD | FLOAT | The royalty fee converted to USD. Example: 127.52 | | TX_FEE | FLOAT | Total fee paid for transaction execution in native token units. Example: 0.002 | | TX_FEE_USD | FLOAT | The transaction fee denominated in USD. Use only one instance per transaction to avoid overcounting. Example: 45.32 | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: * 0xa9059cbb: transfer(address,uint256) * 0x095ea7b3: approve(address,uint256) * 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | EZ\_NFT\_SALES\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Mev Arbitrage](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-mev-arbitrage) [Ez Nft Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers) ⌘I --- # Ez Nft Transfers - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Ez Nft Transfers [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers#commonly-used-fields) * [Sample Queries](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers#columns) **Schema**: `ethereum.nft` **Table**: `ez_nft_transfers` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers#what) What ----------------------------------------------------------------------------------------------- This table contains all NFT transfer events for ERC-721 and ERC-1155 tokens on EVM blockchains. It provides a comprehensive view of NFT movements including transfers, mints, and burns, with enriched metadata for easier analysis. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers#key-use-cases) Key Use Cases ----------------------------------------------------------------------------------------------------------------- * Track daily NFT activity and transfer volume across collections * Analyze NFT minting patterns and mint timing * Identify popular collections by transfer activity * Monitor wallet NFT accumulation and trading behavior * Analyze ERC-1155 batch transfer patterns * Track current NFT holders and ownership changes * Detect burns and unusual transfer patterns [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------- * **Join with ez\_nft\_sales**: Use `tx_hash` to match with sales but note that a single transaction can contain multiple sales. Do not use `event_index` to match as the `event_index` in ez\_nft\_transfers represent the `event_index` of the transfer and not the sale * **Join with dim\_nft\_collection\_metadata**: This is only for the Ethereum blockchain. Use `contract_address` and `token_id` for metadata like traits, token id name and token id description * **Join with fact\_transactions**: Use `tx_hash` for transaction context [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------- * `contract_address`: NFT collection contract address * `token_id`: Unique identifier of the specific NFT * `from_address` / `to_address`: Transfer participants (0x0 for mint/burn) * `is_mint`: Boolean flag for minting events * `token_standard`: NFT standard (erc721, erc1155, cryptopunks, legacy) * `nft_quantity`: Number of tokens transferred (always 1 for ERC-721) * `token_transfer_type`: Specific event type emitted [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers#sample-queries) Sample Queries ------------------------------------------------------------------------------------------------------------------- **Daily NFT Activity Overview** Copy Ask AI SELECT DATE_TRUNC('day', block_timestamp) AS day, COUNT(*) AS total_transfers, COUNT(DISTINCT contract_address) AS unique_collections, COUNT(DISTINCT CASE WHEN is_mint THEN tx_hash END) AS mint_count, COUNT(DISTINCT from_address) AS unique_senders, COUNT(DISTINCT to_address) AS unique_receivers, SUM(IFF(token_standard = 'erc721', 1 , 0)) as erc721_transfer_count, SUM(IFF(token_standard = 'erc1155', 1 , 0)) as erc1155_transfer_count FROM .nft.ez_nft_transfers WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 1 DESC; **Popular NFT Collections by Transfer Volume** Copy Ask AI SELECT contract_address, name, COUNT(*) AS transfer_count, COUNT(DISTINCT token_id) AS unique_tokens, COUNT(DISTINCT from_address) AS unique_senders, COUNT(DISTINCT to_address) AS unique_receivers, SUM(CASE WHEN is_mint THEN 1 ELSE 0 END) AS mints, SUM(CASE WHEN to_address = '0x0000000000000000000000000000000000000000' THEN 1 ELSE 0 END) AS burns FROM .nft.ez_nft_transfers WHERE block_timestamp >= CURRENT_DATE - 7 AND name IS NOT NULL GROUP BY 1, 2 ORDER BY 3 DESC LIMIT 50; **NFT Minting Analysis** Copy Ask AI SELECT contract_address, name, DATE_TRUNC('hour', block_timestamp) AS mint_hour, COUNT(*) AS mint_count, COUNT(DISTINCT to_address) AS unique_minters, COUNT(DISTINCT token_id) as unique_token_id_count FROM .nft.ez_nft_transfers WHERE is_mint = TRUE AND block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2, 3 ORDER BY 4 DESC; **Wallet NFT Activity** Copy Ask AI WITH wallet_activity AS ( SELECT address, SUM(received) AS nfts_received, SUM(sent) AS nfts_sent, SUM(received) - SUM(sent) AS net_change, COUNT(DISTINCT contract_address) AS collections_interacted FROM ( SELECT to_address AS address, COUNT(*) AS received, 0 AS sent, contract_address FROM .nft.ez_nft_transfers WHERE block_timestamp >= CURRENT_DATE - 30 AND to_address != '0x0000000000000000000000000000000000000000' GROUP BY 1, 4 UNION ALL SELECT from_address AS address, 0 AS received, COUNT(*) AS sent, contract_address FROM .nft.ez_nft_transfers WHERE block_timestamp >= CURRENT_DATE - 30 AND from_address != '0x0000000000000000000000000000000000000000' GROUP BY 1, 4 ) GROUP BY 1 ) SELECT * FROM wallet_activity WHERE collections_interacted > 5 ORDER BY net_change DESC LIMIT 100; **ERC-1155 Single and Batch Transfer Analysis** Copy Ask AI SELECT contract_address, name, token_transfer_type, COUNT(*) AS transfer_count FROM .nft.ez_nft_transfers WHERE block_timestamp >= CURRENT_DATE - 7 AND token_transfer_type in ( 'erc1155_TransferSingle', 'erc1155_TransferBatch' ) GROUP BY 1, 2, 3 ORDER BY 4 DESC; **Latest holders for a given ERC-721 collection** Copy Ask AI SELECT to_address, contract_address, token_id FROM .nft.ez_nft_transfers WHERE contract_address = '0xbd3531da5cf5857e7cfaa92426877b022e612cf8' QUALIFY ROW_NUMBER() OVER (PARTITION BY contract_address, token_id ORDER BY block_number DESC, event_index DESC) =1; [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers#columns) Columns ----------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | 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 | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | INTRA_EVENT_INDEX | NUMBER | Position within a batch transfer event, primarily for ERC-1155. Always starts with 1 for single transfers. Example: 1 | | TOKEN_TRANSFER_TYPE | TEXT | The specific event type emitted by the contract. Values include 'erc721_Transfer', 'erc1155_TransferSingle', 'erc1155_TransferBatch', etc. Example: 'erc721_Transfer' | | IS_MINT | BOOLEAN | Boolean flag indicating if this transfer is a minting event (from address is 0x0). Example: true | | FROM_ADDRESS | TEXT | The address sending/transferring the NFT. Special value of '0x0000000000000000000000000000000000000000' indicates minting event. Example: '0x1234567890123456789012345678901234567890' | | TO_ADDRESS | TEXT | The address receiving the NFT. Special value of '0x0000000000000000000000000000000000000000' indicates burning event. Example: '0x1234567890123456789012345678901234567890' | | CONTRACT_ADDRESS | TEXT | The address of the contract that emitted the NFT transfer event. Example: '0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d' | | TOKEN_ID | TEXT | The unique identifier for a specific NFT within a collection. String format to handle various token_id formats. Example: '1234' | | QUANTITY | TEXT | The number of NFTs transferred for this specific token_id. Always 1 for ERC-721, can be more for ERC-1155. Example: 1 | | TOKEN_STANDARD | TEXT | The standard of the NFT. Values include 'erc721', 'erc1155', 'cryptopunks', and 'legacy'. Example: 'erc721' | | NAME | TEXT | The name of the NFT collection. For Ethereum only, join with nft.dim_nft_collection_metadata for token-level details. Example: 'Bored Ape Yacht Club' | | ORIGIN_FUNCTION_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: - 0xa9059cbb: transfer(address,uint256) - 0x095ea7b3: approve(address,uint256) - 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | EZ\_NFT\_TRANSFERS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Nft Sales](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales) [Fact Mev Arbitrage Events](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/fact-mev-arbitrage-events) ⌘I --- # Fact Mev Arbitrage Events - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/fact-mev-arbitrage-events#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Fact Mev Arbitrage Events [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/fact-mev-arbitrage-events#columns) **Schema**: `ethereum.nft` **Table**: `fact_mev_arbitrage_events` **Type**: View This table contains information about the NFTs involved in arbitrage transactions, documenting events from both the buy and sell sides [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/fact-mev-arbitrage-events#columns) Columns -------------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | TRADE\_SIDE | TEXT | The side of the trade that this event represents. This can be either buy or sell. Buy would represent the events where nfts are bought while sell would present the events where the bought nfts are sold. Note that the number of events for buy and sell may not be the same for a given transaction. | | EVENT\_INDEX | FLOAT | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | PLATFORM_NAME | TEXT | The marketplace or platform where the NFT sale occurred. Standardized to lowercase with no spaces. Example: 'opensea' | | PLATFORM_EXCHANGE_VERSION | TEXT | The version identifier of the marketplace contract. Tracks protocol versions and upgrades. Example: 'seaport_1_5' | | BUYER_ADDRESS | TEXT | The blockchain address that purchased the NFT. Example: '0x1234567890123456789012345678901234567890' | | SELLER_ADDRESS | TEXT | The blockchain address that sold the NFT. Example: '0x1234567890123456789012345678901234567890' | | CONTRACT_ADDRESS | TEXT | The smart contract address of the NFT collection. Supports ERC-721, ERC-1155, and custom implementations. Example: '0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d' | | TOKEN_ID | TEXT | The unique identifier of the specific NFT within its collection. Format is numeric string. Example: '1234' | | QUANTITY | TEXT | | | TOKEN_STANDARD | TEXT | The technical standard implemented by the NFT contract. Common values include 'erc721', 'erc1155', 'cryptopunks', and 'legacy'. Example: 'erc721' | | NAME | TEXT | The name of the NFT collection or project. May be NULL for unverified collections. Example: 'Bored Ape Yacht Club' | | EZ_MEV_ARBITRAGE_EVENTS_ID | TEXT | Primary 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(block_number, tx_hash, 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_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Nft Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers) [Price](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/overview) ⌘I --- # Nft - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Nft [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/overview#overview) Overview ----------------------------------------------------------------------------------------------- This schema contains 8 tables and views for Ethereum data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/overview#tables-and-views) Tables and Views --------------------------------------------------------------------------------------------------------------- [Dim Nft Collection Metadata\ ---------------------------\ \ This table contains the metadata for popular NFT collections on the Ethereum blockchain.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/dim-nft-collection-metadata) [Ez Lending Liquidations\ -----------------------\ \ This table contains liquidation events for loans backed by collateralized NFTs on Ethereum.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-liquidations) [Ez Lending Loans\ ----------------\ \ This table contains NFT lending events for loans backed by collateralized NFTs on Ethereum.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-loans) [Ez Lending Repayments\ ---------------------\ \ This table contains repayment events for loans backed by collateralized NFTs on Ethereum.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-lending-repayments) [Ez Mev Arbitrage\ ----------------\ \ This table contains the financial metrics from NFT arbitrage transactions including cost, revenue and profits.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-mev-arbitrage) [Ez Nft Sales\ ------------\ \ This table provides a comprehensive view of NFT (Non-Fungible Token) sales across all major marketplaces and platforms on EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-sales) [Ez Nft Transfers\ ----------------\ \ This table contains all NFT transfer events for ERC-721 and ERC-1155 tokens on EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/ez-nft-transfers) [Fact Mev Arbitrage Events\ -------------------------\ \ This table contains information about the NFTs involved in arbitrage transactions, documenting events from both the buy and sell sides.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/fact-mev-arbitrage-events) Was this page helpful? YesNo [Fact Vat Suck](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/fact-vat-suck) [Dim Nft Collection Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/dim-nft-collection-metadata) ⌘I --- # Ethereum Onchain Data - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Ethereum Ethereum Onchain Data [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/overview#overview) * [Available Schemas](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/overview#available-schemas) [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/overview#overview) Overview ------------------------------------------------------------------------------------------- This section contains comprehensive documentation for all Ethereum data available through Flipside Crypto.[View DBT Documentation\ ----------------------\ \ View the complete technical documentation and data lineage for Ethereum models](https://flipsidecrypto.github.io/ethereum-models/) [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/overview#available-schemas) Available Schemas ------------------------------------------------------------------------------------------------------------- [Core Tables\ -----------\ \ Tables and views in the ethereum.core schema](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/core/overview) [Defi\ ----\ \ Tables and views in the ethereum.defi schema](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/defi/overview) [Ens\ ---\ \ Tables and views in the ethereum.ens schema](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/ens/overview) [L2\ --\ \ Tables and views in the ethereum.l2 schema](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/l2/overview) [Maker\ -----\ \ Tables and views in the ethereum.maker schema](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/maker/overview) [Nft\ ---\ \ Tables and views in the ethereum.nft schema](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/overview) [Price\ -----\ \ Tables and views in the ethereum.price schema](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/overview) Was this page helpful? YesNo [Ez Core Metrics Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/eclipse/stats/ez-core-metrics-hourly) [Balances](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/balances/overview) ⌘I --- # Dim Asset Metadata - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Dim Asset Metadata [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata#commonly-used-fields) * [Sample Queries](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata#columns) **Schema**: `ethereum.price` **Table**: `dim_asset_metadata` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata#what) What --------------------------------------------------------------------------------------------------- This table provides comprehensive metadata for all assets (tokens and native assets) tracked in the price schema across EVM blockchains. It includes provider, asset identifiers, names, symbols, contract addresses, blockchain, and verification status. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata#key-use-cases) Key Use Cases --------------------------------------------------------------------------------------------------------------------- * Join price data to asset metadata for enriched analysis * Cross-chain asset analysis and mapping * Asset discovery and verification status checking * Provider-specific data source analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata#important-relationships) Important Relationships ----------------------------------------------------------------------------------------------------------------------------------------- * **Join with ez\_prices\_hourly**: For price time series data * **Join with core.dim\_contracts**: For contract metadata [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata#commonly-used-fields) Commonly-used Fields ----------------------------------------------------------------------------------------------------------------------------------- * `provider`: Data source (coingecko, coinmarketcap, etc.) * `asset_id`: Provider-specific unique identifier * `blockchain`: Network identifier * `token_address`: Contract address (NULL for native assets) * `symbol`: Token ticker symbol * `name`: Full asset name [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata#sample-queries) Sample Queries ----------------------------------------------------------------------------------------------------------------------- **Basic Asset Lookup** Copy Ask AI SELECT * FROM .price.dim_asset_metadata WHERE blockchain = 'ethereum' ORDER BY symbol; [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata#columns) Columns --------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | TOKEN\_ADDRESS | TEXT | Contract address of the token on the blockchain. NULL for native assets (ETH, AVAX, etc.). | Example: ‘0xa0b86a33e6776a1e7f9f0b8b8b8b8b8b8b8b8b8b’ | | ASSET\_ID | TEXT | Unique identifier for the asset from the price provider. Provider-specific ID format. Example: ‘ethereum’ | | SYMBOL | TEXT | Token ticker symbol as commonly recognized. Usually 3-5 uppercase characters. Example: ‘WETH’ | | NAME | TEXT | Full name of the asset or token. More descriptive than symbol. Example: ‘Wrapped Ether’ | | BLOCKCHAIN | TEXT | The blockchain network where the asset exists. Lowercase by convention. Example: ‘ethereum’ | | BLOCKCHAIN\_ID | TEXT | The numeric or string identifier for the blockchain on which the asset exists. Used for cross-chain mapping. Example: ‘1’ | | PROVIDER | TEXT | Data source that provided the price information. Values include ‘coingecko’, ‘coinmarketcap’, ‘dex\_aggregated’. Example: ‘coingecko’ | | DIM\_ASSET\_METADATA\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Price](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/overview) [Ez Asset Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata) ⌘I --- # Ez Asset Metadata - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Ez Asset Metadata [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata#commonly-used-fields) * [Sample Queries](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata#columns) **Schema**: `ethereum.price` **Table**: `ez_asset_metadata` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata#what) What -------------------------------------------------------------------------------------------------- This curated dimensional table provides comprehensive metadata for tokens and native assets across EVM blockchains. It serves as the authoritative source for asset information, with quality checks and verification status to ensure reliability. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata#key-use-cases) Key Use Cases -------------------------------------------------------------------------------------------------------------------- * Asset discovery and verification checking * Cross-chain asset mapping and analysis * Token metadata lookup for display purposes * Filtering for verified or native assets only [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata#important-relationships) Important Relationships ---------------------------------------------------------------------------------------------------------------------------------------- * **Join with ez\_prices\_hourly**: For price data enrichment * **Join with ez\_token\_transfers**: For transfer metadata [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata#commonly-used-fields) Commonly-used Fields ---------------------------------------------------------------------------------------------------------------------------------- * `token_address`: Contract address (NULL for native assets) * `symbol`: Token ticker symbol * `name`: Full asset name * `decimals`: Token decimal places * `is_verified`: Flipside verification status * `is_native`: Native asset flag * `blockchain`: Network identifier [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata#sample-queries) Sample Queries ---------------------------------------------------------------------------------------------------------------------- **Verified Asset Discovery** Copy Ask AI -- Find all verified USD stablecoins SELECT blockchain, token_address, name, symbol, decimals, is_verified FROM .price.ez_asset_metadata WHERE is_verified = TRUE AND ( symbol IN ('USDC', 'USDT', 'DAI', 'BUSD') OR name ILIKE '%USD%' OR name ILIKE '%stablecoin%' ) AND is_native = FALSE ORDER BY blockchain, symbol; **Cross-Chain Asset Mapping** Copy Ask AI -- Find same assets across multiple chains WITH asset_presence AS ( SELECT symbol, name, COUNT(DISTINCT blockchain) AS chain_count, ARRAY_AGG(DISTINCT blockchain) AS chains, ARRAY_AGG(token_address) AS addresses FROM .price.ez_asset_metadata WHERE is_native = FALSE AND is_verified = TRUE GROUP BY 1, 2 ) SELECT * FROM asset_presence WHERE chain_count > 3 ORDER BY chain_count DESC, symbol; **Native Asset Reference** Copy Ask AI -- Get all native assets with metadata SELECT blockchain, symbol, name, decimals, CASE blockchain WHEN 'ethereum' THEN 'Proof of Stake' WHEN 'binance' THEN 'Proof of Staked Authority' WHEN 'polygon' THEN 'Proof of Stake' WHEN 'avalanche' THEN 'Avalanche Consensus' ELSE 'Various' END AS consensus_mechanism FROM .price.ez_asset_metadata WHERE is_native = TRUE ORDER BY blockchain; [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata#columns) Columns -------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | TOKEN\_ADDRESS | TEXT | Contract address of the token on the blockchain. NULL for native assets (ETH, AVAX, etc.). | Example: ‘0xa0b86a33e6776a1e7f9f0b8b8b8b8b8b8b8b8b8b’ | | ASSET\_ID | TEXT | Unique identifier for the asset from the price provider. Provider-specific ID format. Example: ‘ethereum’ | | SYMBOL | TEXT | Token ticker symbol as commonly recognized. Usually 3-5 uppercase characters. Example: ‘WETH’ | | NAME | TEXT | Full name of the asset or token. More descriptive than symbol. Example: ‘Wrapped Ether’ | | DECIMALS | NUMBER | Number of decimal places for the token. Most ERC-20 tokens use 18 decimals, USDC/USDT use 6, WBTC uses 8. Example: 18 | | BLOCKCHAIN | TEXT | The blockchain network where the asset exists. Lowercase by convention. Example: ‘ethereum’ | | IS\_NATIVE | BOOLEAN | Boolean indicating if the asset is the blockchain’s native currency. TRUE for ETH on Ethereum, AVAX on Avalanche, etc. Example: true | | IS\_DEPRECATED | BOOLEAN | Flag indicating if the asset is no longer actively supported. TRUE for deprecated assets that may have stale prices. Example: false | | IS\_VERIFIED | BOOLEAN | Boolean indicating Flipside team verification of the asset. TRUE for manually verified assets with validated metadata. Example: true | | IS\_VERIFIED\_MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | | EZ\_ASSET\_METADATA\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Dim Asset Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata) [Ez Prices Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly) ⌘I --- # Ez Prices Hourly - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Ez Prices Hourly [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly#commonly-used-fields) * [Sample Queries](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly#columns) **Schema**: `ethereum.price` **Table**: `ez_prices_hourly` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly#what) What ------------------------------------------------------------------------------------------------- This curated table provides reliable hourly price data for tokens and native assets across EVM blockchains. It combines multiple data sources with quality checks to ensure accurate, consistent pricing for DeFi analytics, portfolio valuations, and historical analysis. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------------- * Calculate USD values for token transfers and transaction amounts * Track price volatility and market movements over time * Monitor stablecoin depegging events and price stability * Analyze native asset price trends across different blockchains * Perform portfolio valuations and historical price lookups * Create price charts and technical analysis dashboards * Assess price data quality and imputation rates [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly#important-relationships) Important Relationships --------------------------------------------------------------------------------------------------------------------------------------- * **Join with ez\_token\_transfers**: Calculate transfer USD values using hourly price snapshots * **Join with ez\_asset\_metadata**: Get token details and verification status * **Join with dim\_contracts**: Match addresses with contract metadata [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly#commonly-used-fields) Commonly-used Fields --------------------------------------------------------------------------------------------------------------------------------- * `hour`: UTC timestamp truncated to hour for price recording * `token_address`: Contract address of the token (NULL for native assets) * `symbol`: Token ticker symbol (ETH, USDC, etc.) * `price`: USD price of one whole token unit * `is_imputed`: Flag indicating forward-filled prices due to missing data * `is_native`: Boolean for blockchain native currencies * `blockchain`: Network where the asset exists [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly#sample-queries) Sample Queries --------------------------------------------------------------------------------------------------------------------- **Token Price Lookup with USD Calculations** Copy Ask AI -- Calculate USD value for token transfers SELECT t.block_timestamp, t.tx_hash, t.symbol, t.from_address, t.to_address, t.amount, p.price, t.amount * p.price AS usd_value, p.is_imputed FROM .core.ez_token_transfers t JOIN .price.ez_prices_hourly p ON t.contract_address = p.token_address AND DATE_TRUNC('hour', t.block_timestamp) = p.hour WHERE t.block_timestamp >= CURRENT_DATE - 7 AND t.amount > 0 AND p.price IS NOT NULL ORDER BY usd_value DESC LIMIT 100; **Price Volatility Analysis** Copy Ask AI -- 24-hour price volatility for major tokens WITH price_stats AS ( SELECT symbol, token_address, DATE(hour) AS date, MIN(price) AS daily_low, MAX(price) AS daily_high, AVG(price) AS daily_avg, STDDEV(price) AS daily_stddev, (MAX(price) - MIN(price)) / MIN(price) * 100 AS daily_range_pct FROM .price.ez_prices_hourly WHERE hour >= CURRENT_DATE - 30 AND symbol IN ('WETH', 'USDC', 'USDT', 'WBTC', 'DAI') AND NOT is_imputed GROUP BY 1, 2, 3 ) SELECT symbol, AVG(daily_range_pct) AS avg_daily_volatility, MAX(daily_range_pct) AS max_daily_volatility, AVG(daily_stddev / daily_avg) * 100 AS avg_cv_pct FROM price_stats GROUP BY 1 ORDER BY 2 DESC; **Native Asset Price Tracking** Copy Ask AI -- Track native asset prices across chains SELECT blockchain, symbol, hour, price, price / LAG(price, 24) OVER (PARTITION BY blockchain ORDER BY hour) - 1 AS change_24h, price / LAG(price, 168) OVER (PARTITION BY blockchain ORDER BY hour) - 1 AS change_7d FROM .price.ez_prices_hourly WHERE is_native = TRUE AND hour >= CURRENT_DATE - 8 AND hour = DATE_TRUNC('hour', CURRENT_TIMESTAMP) - INTERVAL '1 hour' ORDER BY blockchain; **Stablecoin Peg Monitoring** Copy Ask AI -- Monitor stablecoin deviations from $1 SELECT symbol, hour, price, ABS(price - 1.0) AS deviation, CASE WHEN ABS(price - 1.0) > 0.05 THEN 'Severe Depeg' WHEN ABS(price - 1.0) > 0.01 THEN 'Mild Depeg' ELSE 'Stable' END AS peg_status FROM .price.ez_prices_hourly WHERE symbol IN ('USDC', 'USDT', 'DAI', 'BUSD', 'FRAX', 'LUSD') AND hour >= CURRENT_DATE - 7 AND ABS(price - 1.0) > 0.005 ORDER BY hour DESC, deviation DESC; **Price Data Quality Check** Copy Ask AI -- Analyze price data completeness and imputation rates SELECT symbol, COUNT(*) AS total_hours, SUM(CASE WHEN is_imputed THEN 1 ELSE 0 END) AS imputed_hours, ROUND(100.0 * SUM(CASE WHEN is_imputed THEN 1 ELSE 0 END) / COUNT(*), 2) AS imputation_rate, MIN(hour) AS first_price, MAX(hour) AS last_price, COUNT(DISTINCT DATE(hour)) AS days_with_data FROM .price.ez_prices_hourly WHERE hour >= CURRENT_DATE - 30 GROUP BY 1 HAVING COUNT(*) > 100 ORDER BY imputation_rate DESC; [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly#columns) Columns ------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | HOUR | TIMESTAMP\_NTZ | UTC timestamp truncated to the hour for price recording. Used for joining with hourly transaction data. | Example: ‘2024-01-15 14:00:00.000’ | | TOKEN\_ADDRESS | TEXT | Contract address of the token on the blockchain. NULL for native assets (ETH, AVAX, etc.). Example: ‘0xa0b86a33e6776a1e7f9f0b8b8b8b8b8b8b8b8b8b’ | | SYMBOL | TEXT | Token ticker symbol as commonly recognized. Usually 3-5 uppercase characters. Example: ‘WETH’ | | NAME | TEXT | | | DECIMALS | NUMBER | Number of decimal places for the token. Most ERC-20 tokens use 18 decimals, USDC/USDT use 6, WBTC uses 8. Example: 18 | | PRICE | FLOAT | USD price of one whole token unit at the recorded hour. Example: 3000.50 | | BLOCKCHAIN | TEXT | The blockchain network where the asset exists. Lowercase by convention. Example: ‘ethereum’ | | IS\_NATIVE | BOOLEAN | Boolean indicating if the asset is the blockchain’s native currency. TRUE for ETH on Ethereum, AVAX on Avalanche, etc. Example: true | | IS\_IMPUTED | BOOLEAN | Boolean flag indicating if the price was forward-filled due to missing data. TRUE means price carried forward from last known value. Example: false | | IS\_DEPRECATED | BOOLEAN | Flag indicating if the asset is no longer actively supported. TRUE for deprecated assets that may have stale prices. Example: false | | IS\_VERIFIED | BOOLEAN | Boolean indicating Flipside team verification of the asset. TRUE for manually verified assets with validated metadata. Example: true | | EZ\_PRICES\_HOURLY\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Asset Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata) [Fact Prices Ohlc Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly) ⌘I --- # Fact Prices Ohlc Hourly - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Fact Prices Ohlc Hourly [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly#commonly-used-fields) * [Sample Queries](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly#columns) **Schema**: `ethereum.price` **Table**: `fact_prices_ohlc_hourly` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly#what) What -------------------------------------------------------------------------------------------------------- This table provides hourly OHLC (Open, High, Low, Close) price data for all assets tracked in the price schema. It is designed for time series analysis, volatility studies, and historical price lookups. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly#key-use-cases) Key Use Cases -------------------------------------------------------------------------------------------------------------------------- * Technical analysis and candlestick chart creation * Volatility studies and risk assessment * Historical price lookups and trend analysis * Market timing and trading analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly#important-relationships) Important Relationships ---------------------------------------------------------------------------------------------------------------------------------------------- * **Join with dim\_asset\_metadata**: For asset metadata * **Join with ez\_token\_transfers**: For USD value calculations [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly#commonly-used-fields) Commonly-used Fields ---------------------------------------------------------------------------------------------------------------------------------------- * `hour`: UTC timestamp for the price period * `asset_id`: Unique identifier for the asset * `open`: Opening price at start of hour * `high`: Highest price during hour * `low`: Lowest price during hour * `close`: Closing price at end of hour [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly#sample-queries) Sample Queries ---------------------------------------------------------------------------------------------------------------------------- **OHLC Data Retrieval** Copy Ask AI SELECT hour, asset_id, open, high, low, close FROM .price.fact_prices_ohlc_hourly WHERE asset_id = '' AND hour >= CURRENT_DATE - 30 ORDER BY hour DESC; [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly#columns) Columns -------------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | ASSET\_ID | TEXT | Unique identifier for the asset from the price provider. Provider-specific ID format. | Example: ‘ethereum’ | | HOUR | TIMESTAMP\_NTZ | UTC timestamp truncated to the hour for price recording. Used for joining with hourly transaction data. Example: ‘2024-01-15 14:00:00.000’ | | OPEN | FLOAT | Opening price at the start of the hour in USD. First recorded price in the hour for OHLC analysis. Example: 2995.25 | | HIGH | FLOAT | Highest price reached during the hour in USD. Maximum price in the hour for volatility analysis. Example: 3005.75 | | LOW | FLOAT | Lowest price reached during the hour in USD. Minimum price in the hour for support level analysis. Example: 2985.50 | | CLOSE | FLOAT | Closing price at the end of the hour in USD. Last recorded price in the hour, commonly used for valuations. Example: 3000.50 | | PROVIDER | TEXT | | | FACT\_PRICES\_OHLC\_HOURLY\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Prices Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly) [Flow Data](https://docs.flipsidecrypto.xyz/blockchain-data/flow/overview) ⌘I --- # Price - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Price [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/overview#overview) Overview ------------------------------------------------------------------------------------------------- This schema contains 4 tables and views for Ethereum data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/overview#tables-and-views) Tables and Views ----------------------------------------------------------------------------------------------------------------- [Dim Asset Metadata\ ------------------\ \ This table provides comprehensive metadata for all assets (tokens and native assets) tracked in the price schema across EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata) [Ez Asset Metadata\ -----------------\ \ This curated dimensional table provides comprehensive metadata for tokens and native assets across EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-asset-metadata) [Ez Prices Hourly\ ----------------\ \ This curated table provides reliable hourly price data for tokens and native assets across EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/ez-prices-hourly) [Fact Prices Ohlc Hourly\ -----------------------\ \ This table provides hourly OHLC (Open, High, Low, Close) price data for all assets tracked in the price schema.](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly) Was this page helpful? YesNo [Fact Mev Arbitrage Events](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/nft/fact-mev-arbitrage-events) [Dim Asset Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/dim-asset-metadata) ⌘I --- # Dim Nfl Teams - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Beta Dim Nfl Teams [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [beta\_\_dim\_nfl\_teams](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams#beta-dim-nfl-teams) * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams#columns) **Schema**: `flow.beta` **Table**: `dim_nfl_teams` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams#beta-dim-nfl-teams) beta\_\_dim\_nfl\_teams ========================================================================================================================== [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams#description) Description ------------------------------------------------------------------------------------------------------- A beta-dimensional table containing NFL team metadata from the ESPN Teams Endpoint. This table serves as an experimental data source for NFL AllDay NFT analytics and team-related analysis. The table is in beta mode and subject to change, providing team information that may be used for NFT moment analysis, team performance tracking, and sports analytics. Due to its experimental nature, this table should not be used for production purposes without accepting the risk of sudden changes or deletion. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams#key-use-cases) Key Use Cases ----------------------------------------------------------------------------------------------------------- * **NFL AllDay Analytics**: Supporting NFT moment analysis and team-related NFT performance tracking * **Team Research**: Providing team metadata for sports analytics and team performance analysis * **Experimental Features**: Supporting beta features and experimental analytics in the sports NFT space * **Data Exploration**: Investigating potential use cases for team data in blockchain applications * **Prototype Development**: Supporting prototype development for sports-related blockchain features [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------- * **beta\_\_dim\_nfl\_athletes**: Links to athlete information for team-athlete relationship analysis * **beta\_\_dim\_nflad\_playoff\_rosters**: May link to playoff roster information for seasonal analysis * **nft\_\_dim\_moment\_metadata**: May overlap with NFL AllDay NFT moment data * **beta\_\_ez\_moment\_player\_ids**: May provide additional team identification and linking capabilities [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------- * **Team identification fields**: For team identification and analysis * **League association fields**: For team-league relationship analysis * **Metadata fields**: For team information and categorization [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams#columns) Columns ----------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | REF | TEXT | | | ID | TEXT | | | GUID | TEXT | | | UID | TEXT | | | ALTERNATE\_IDS | TEXT | | | SLUG | TEXT | | | LOCATION | TEXT | | | NAME | TEXT | | | NICKNAME | TEXT | | | ABBREVIATION | TEXT | | | DISPLAY\_NAME | TEXT | | | SHORT\_DISPLAY\_NAME | TEXT | | | COLOR | TEXT | | | ALTERNATE\_COLOR | TEXT | | | IS\_ACTIVE | BOOLEAN | | | IS\_ALL\_STAR | BOOLEAN | | | LOGOS | TEXT | | | RECORD | TEXT | | | ODDS\_RECORDS | TEXT | | | ATHLETES | TEXT | | | VENUE | TEXT | | | GROUPS | TEXT | | | RANKS | TEXT | | | STATISTICS | TEXT | | | LEADERS | TEXT | | | LINKS | TEXT | | | INJURIES | TEXT | | | NOTES | TEXT | | | AGAINST\_THE\_SPREAD\_RECORDS | TEXT | | | FRANCHISE | TEXT | | | DEPTH\_CHARTS | TEXT | | | PROJECTION | TEXT | | | EVENTS | TEXT | | | TRANSACTIONS | TEXT | | | COACHES | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | Was this page helpful? YesNo [Dim Nfl Athletes](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes) [Dim Nflad Playoff Rosters](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters) ⌘I --- # Dim Nfl Athletes - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Beta Dim Nfl Athletes [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [beta\_\_dim\_nfl\_athletes](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes#beta-dim-nfl-athletes) * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes#columns) **Schema**: `flow.beta` **Table**: `dim_nfl_athletes` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes#beta-dim-nfl-athletes) beta\_\_dim\_nfl\_athletes =================================================================================================================================== [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes#description) Description ---------------------------------------------------------------------------------------------------------- A beta-dimensional table containing NFL athlete metadata from the ESPN Athletes Endpoint. This table serves as an experimental data source for NFL AllDay NFT analytics and athlete-related analysis. The table is in beta mode and subject to change, providing athlete information that may be used for NFT moment analysis, player performance tracking, and sports analytics. Due to its experimental nature, this table should not be used for production purposes without accepting the risk of sudden changes or deletion. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes#key-use-cases) Key Use Cases -------------------------------------------------------------------------------------------------------------- * **NFL AllDay Analytics**: Supporting NFT moment analysis and athlete-related NFT performance tracking * **Player Research**: Providing athlete metadata for sports analytics and player performance analysis * **Experimental Features**: Supporting beta features and experimental analytics in the sports NFT space * **Data Exploration**: Investigating potential use cases for athlete data in blockchain applications * **Prototype Development**: Supporting prototype development for sports-related blockchain features [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes#important-relationships) Important Relationships ---------------------------------------------------------------------------------------------------------------------------------- * **beta\_\_dim\_nfl\_teams**: Links to team information for athlete-team relationship analysis * **beta\_\_dim\_nflad\_playoff\_rosters**: May link to playoff roster information for seasonal analysis * **nft\_\_dim\_moment\_metadata**: May overlap with NFL AllDay NFT moment data * **beta\_\_ez\_moment\_player\_ids**: May provide additional player identification and linking capabilities [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes#commonly-used-fields) Commonly-used Fields ---------------------------------------------------------------------------------------------------------------------------- * **Athlete identification fields**: For player identification and analysis * **Team association fields**: For athlete-team relationship analysis * **Metadata fields**: For athlete information and categorization [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes#columns) Columns -------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | REF | TEXT | | | ID | TEXT | | | UID | TEXT | | | GUID | TEXT | | | TYPE | TEXT | | | ALTERNATE\_IDS | TEXT | | | FIRST\_NAME | TEXT | | | LAST\_NAME | TEXT | | | FULL\_NAME | TEXT | | | DISPLAY\_NAME | TEXT | | | SHORT\_NAME | TEXT | | | WEIGHT | FLOAT | | | DISPLAY\_WEIGHT | TEXT | | | HEIGHT | FLOAT | | | DISPLAY\_HEIGHT | TEXT | | | AGE | FLOAT | | | DATE\_OF\_BIRTH | TEXT | | | LINKS | TEXT | | | BIRTH\_PLACE | TEXT | | | COLLEGE | TEXT | | | SLUG | TEXT | | | HEADSHOT | TEXT | | | JERSEY | TEXT | | | POSITION | TEXT | | | LINKED | BOOLEAN | | | TEAM | TEXT | | | STATISTICS | TEXT | | | CONTRACTS | TEXT | | | EXPERIENCE | TEXT | | | COLLEGE\_ATHLETE | TEXT | | | ACTIVE | BOOLEAN | | | DRAFT | TEXT | | | STATUS | TEXT | | | STATISTICSLOG | TEXT | | | DEBUT\_YEAR | FLOAT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | Was this page helpful? YesNo [Beta](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/overview) [Dim Nfl Teams](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams) ⌘I --- # Dim Nflad Playoff Rosters - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Beta Dim Nflad Playoff Rosters [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [beta\_\_dim\_nflad\_playoff\_rosters](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters#beta-dim-nflad-playoff-rosters) * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters#columns) **Schema**: `flow.beta` **Table**: `dim_nflad_playoff_rosters` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters#beta-dim-nflad-playoff-rosters) beta\_\_dim\_nflad\_playoff\_rosters =============================================================================================================================================================== [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters#description) Description ------------------------------------------------------------------------------------------------------------------- A temporary dimensional table containing official rosters for the Flipside x NFL AllDay Playoff Challenge. This table serves as a specialized data source for playoff-specific NFT analytics and roster management during the NFL playoff season. The table is designed to support the playoff challenge by providing accurate roster information for participating teams and players. Due to its temporary nature, this table may be removed or significantly modified after the playoff challenge concludes. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters#key-use-cases) Key Use Cases ----------------------------------------------------------------------------------------------------------------------- * **Playoff Challenge Support**: Providing roster data for the Flipside x NFL AllDay Playoff Challenge * **Playoff Analytics**: Supporting playoff-specific NFT moment analysis and performance tracking * **Roster Management**: Maintaining accurate roster information for playoff participants * **Challenge Validation**: Supporting challenge rules and participant validation * **Seasonal Analysis**: Providing playoff-specific data for seasonal sports analytics [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------------- * **beta\_\_dim\_nfl\_athletes**: Links to athlete information for roster-athlete relationship analysis * **beta\_\_dim\_nfl\_teams**: Links to team information for roster-team relationship analysis * **nft\_\_dim\_moment\_metadata**: May overlap with NFL AllDay playoff moment data * **beta\_\_ez\_moment\_player\_ids**: May provide additional player identification for playoff rosters [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------------- * **Roster identification fields**: For roster identification and challenge management * **Player association fields**: For roster-player relationship analysis * **Team association fields**: For roster-team relationship analysis * **Playoff-specific fields**: For playoff challenge and seasonal analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters#columns) Columns ----------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | WALLET | TEXT | | | ID\_0 | TEXT | | | ID\_1 | TEXT | | | ID\_2 | TEXT | | | ID\_3 | TEXT | | | ID\_4 | TEXT | | | ID\_5 | TEXT | | | ID\_6 | TEXT | | | ID\_7 | TEXT | | | ID\_8 | TEXT | | | ID\_9 | TEXT | | | CAMPAIGN | TEXT | | Was this page helpful? YesNo [Dim Nfl Teams](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams) [Ez Moment Player Ids](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/ez-moment-player-ids) ⌘I --- # Ez Moment Player Ids - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/ez-moment-player-ids#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Beta Ez Moment Player Ids [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/ez-moment-player-ids#columns) **Schema**: `flow.beta` **Table**: `ez_moment_player_ids` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/ez-moment-player-ids#columns) Columns ------------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | NFT\_ID | TEXT | | | NFLALLDAY\_ID | TEXT | | | SERIAL\_NUMBER | NUMBER | | | MOMENT\_TIER | TEXT | | | PLAYER | TEXT | | | TEAM | TEXT | | | SEASON | TEXT | | | PLAY\_TYPE | TEXT | | | POSITION | TEXT | | | ESPN\_PLAYER\_ID | TEXT | | | ESPN\_TEAM\_ID | NUMBER | | | IS\_ACTIVE | BOOLEAN | | Was this page helpful? YesNo [Dim Nflad Playoff Rosters](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters) [Core Tables](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/overview) ⌘I --- # Beta - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Beta Beta [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/overview#overview) Overview -------------------------------------------------------------------------------------------- This schema contains 4 tables and views for Flow data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/overview#tables-and-views) Tables and Views ------------------------------------------------------------------------------------------------------------ [Dim Nfl Athletes\ ----------------\ \ A beta-dimensional table containing NFL athlete metadata from the ESPN Athletes Endpoint.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes) [Dim Nfl Teams\ -------------\ \ A beta-dimensional table containing NFL team metadata from the ESPN Teams Endpoint.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-teams) [Dim Nflad Playoff Rosters\ -------------------------\ \ A temporary dimensional table containing official rosters for the Flipside x NFL AllDay Playoff Challenge.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nflad-playoff-rosters) [Ez Moment Player Ids\ --------------------\ \ Data from Ez Moment Player Ids](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/ez-moment-player-ids) Was this page helpful? YesNo [Flow Data](https://docs.flipsidecrypto.xyz/blockchain-data/flow/overview) [Dim Nfl Athletes](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/dim-nfl-athletes) ⌘I --- # Dim Contract Abis - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contract-abis#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core EVM Dim Contract Abis [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contract-abis#columns) **Schema**: `flow.core_evm` **Table**: `dim_contract_abis` **Type**: Base Table This table contains the contract ABIs that we have sourced from Etherscan, the community, or bytecode matched. This table is the source of ABIs used in the `core__ez_decoded_event_logs` table. We first try to source ABIs from Etherscan. If we cannot find an ABI on Etherscan, we will rely on user submissions. To add a contract to this table, please visit [here](https://science.flipsidecrypto.xyz/abi-requestor/) . If we are unable to locate an ABI for a contract from Etherscan or the community, we will try to find an ABI to use by matching the contract bytecode to a known contract bytecode we do have an ABI for. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contract-abis#columns) Columns ------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | CONTRACT\_ADDRESS | TEXT | The unique address of the deployed contract. | | ABI | VARIANT | The JSON ABI for the contract. | | ABI\_SOURCE | TEXT | The source of the ABI. This can be the block explorer, `user_submitted`, or `bytecode_matched`. | | BYTECODE | TEXT | The deployed bytecode of the contract. | | DIM\_CONTRACT\_ABIS\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | Was this page helpful? YesNo [Core Evm](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/overview) [Dim Contracts](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts) ⌘I --- # Dim Contracts - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core EVM Dim Contracts [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts#columns) **Schema**: `flow.core_evm` **Table**: `dim_contracts` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts#description) Description ----------------------------------------------------------------------------------------------------------- A dimensional table containing metadata for smart contracts deployed on EVM-compatible blockchains. This table serves as the foundation for contract identification and analysis, providing information about contract addresses, names, symbols, decimals, and creation details. The table supports contract analysis, token identification, and smart contract ecosystem understanding across multiple EVM chains. Each record represents a unique contract with comprehensive metadata and deployment information. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts#key-use-cases) Key Use Cases --------------------------------------------------------------------------------------------------------------- * **Contract Identification**: Identifying and categorizing smart contracts across EVM chains * **Token Analysis**: Understanding token contracts, their properties, and metadata * **Contract Creation Tracking**: Monitoring new contract deployments and creation patterns * **Contract Ecosystem Analysis**: Understanding the distribution and types of contracts * **Cross-Chain Contract Analysis**: Comparing contracts across different EVM-compatible blockchains * **Contract Attribution**: Identifying contract creators and deployment patterns [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts#important-relationships) Important Relationships ----------------------------------------------------------------------------------------------------------------------------------- * **core\_evm\_\_fact\_transactions**: Links to transactions involving these contracts * **core\_evm\_\_fact\_event\_logs**: Links to events emitted by these contracts * **core\_evm\_\_fact\_traces**: Links to execution traces involving these contracts * **core\_evm\_\_dim\_labels**: Links to contract labels for additional categorization * **core\_evm\_\_ez\_token\_transfers**: Links to token transfers involving these contracts * **core\_\_dim\_contract\_labels**: May provide comparison data with native Flow contracts [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts#commonly-used-fields) Commonly-used Fields ----------------------------------------------------------------------------------------------------------------------------- * **ADDRESS**: Essential for contract identification and cross-table joins * **NAME**: Important for contract identification and user interface display * **SYMBOL**: Critical for token contracts and trading interface support * **DECIMALS**: Key for token amount calculations and precision handling * **CREATED\_BLOCK\_NUMBER**: Important for contract creation tracking and temporal analysis * **CREATOR\_ADDRESS**: Critical for contract attribution and creator analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts#columns) Columns --------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | ADDRESS | TEXT | The unique address of the deployed contract. | | SYMBOL | TEXT | The symbol used to represent this contract. Please note this is not necessarily unique. | | NAME | TEXT | The name of the deployed contract. Please note this is not necessarily unique. | | DECIMALS | NUMBER | The decimals for the token contract. | | CREATED\_BLOCK\_NUMBER | NUMBER | The block number at which the contract was read and details recorded. | | CREATED\_BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The block timestamp at which the contract was read and details recorded. | | CREATED\_TX\_HASH | TEXT | The transaction hash at which the contract was created. | | CREATOR\_ADDRESS | TEXT | The address of the contract creator. | | DIM\_CONTRACTS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was last modified. | Was this page helpful? YesNo [Dim Contract Abis](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contract-abis) [Dim Labels](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels) ⌘I --- # Dim Labels - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core EVM Dim Labels [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels#columns) **Schema**: `flow.core_evm` **Table**: `dim_labels` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels#description) Description -------------------------------------------------------------------------------------------------------- A dimensional table containing address labels and categorization data for EVM-compatible blockchains. This table serves as the foundation for address identification and categorization, providing human-readable names and labels for addresses including contracts, users, and protocols. The table supports address analysis, user identification, and ecosystem understanding across multiple EVM chains. Each record represents a labeled address with comprehensive categorization and metadata. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------ * **Address Identification**: Providing human-readable names for blockchain addresses * **User Analysis**: Identifying and categorizing user addresses and their activities * **Protocol Analysis**: Understanding protocol addresses and their roles in the ecosystem * **Contract Categorization**: Labeling and categorizing smart contract addresses * **Cross-Chain Labeling**: Maintaining consistent labels across different EVM-compatible blockchains * **Ecosystem Mapping**: Understanding the relationships and roles of different addresses [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels#important-relationships) Important Relationships -------------------------------------------------------------------------------------------------------------------------------- * **core\_evm\_\_fact\_transactions**: Links to transactions involving labeled addresses * **core\_evm\_\_fact\_event\_logs**: Links to events involving labeled addresses * **core\_evm\_\_dim\_contracts**: Links to contract metadata for labeled contract addresses * **core\_evm\_\_ez\_token\_transfers**: Links to token transfers involving labeled addresses * **core\_evm\_\_ez\_native\_transfers**: Links to native transfers involving labeled addresses * **core\_\_dim\_labels**: May provide comparison data with native Flow labels [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels#commonly-used-fields) Commonly-used Fields -------------------------------------------------------------------------------------------------------------------------- * **ADDRESS**: Essential for address identification and cross-table joins * **ADDRESS\_NAME**: Critical for human-readable address identification * **LABEL\_TYPE**: Important for address categorization and filtering * **LABEL\_SUBTYPE**: Key for detailed address categorization and analysis * **LABEL**: Essential for address labeling and user interface display * **BLOCKCHAIN**: Critical for cross-chain analysis and chain-specific labeling [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels#columns) Columns ------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | BLOCKCHAIN | TEXT | The name of the blockchain. | | CREATOR | TEXT | The name of the creator of the label. | | ADDRESS | TEXT | Address that the label is for. This is the field that should be used to join other tables with labels. | | ADDRESS\_NAME | TEXT | The most granular label for this address. | | LABEL\_TYPE | TEXT | A high-level category describing the address’s main function or ownership. | | LABEL\_SUBTYPE | TEXT | A sub-category nested within label type providing further detail. | | LABEL | TEXT | The label for this address. | | DIM\_LABELS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was last modified. | Was this page helpful? YesNo [Dim Contracts](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts) [Ez Decoded Event Logs](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-decoded-event-logs) ⌘I --- # Ez Decoded Event Logs - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-decoded-event-logs#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core EVM Ez Decoded Event Logs [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) **Schema**: `flow.core_evm` **Table**: `ez_decoded_event_logs` **Type**: Base Table For information on how to submit a contract for decoding, as well as how ABIs are sourced, please visit [here](https://science.flipsidecrypto.xyz/abi-requestor/) . This model contains decoded event logs for contracts that we have an ABI for. Please note, this table does not include all event logs, only those that we have an ABI for. The `decoded_log` column is the easiest place to query decoded data. It is a JSON object, where the keys are the names of the event parameters, and the values are the values of the event parameters. You can select from this column using the following sample format, `decoded_log:from::string` or more generally, `decoded_log:::datatype`. See below for a full sample query. The `full_decoded_logs` column contains the same information, as well as additional fields such as the datatype of the decoded data. You may need to laterally flatten this column to query the data. Sample query for USDC Transfer events: Copy Ask AI select tx_hash, block_number, contract_address, decoded_log:from::string as from_address, decoded_log:to::string as to_address, decoded_log:value::integer as value from ethereum.core.fact_decoded_event_logs where contract_address = lower('0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48') and block_number between 16400000 and 16405000 and event_name = 'Transfer' limit 50``` ## Columns | Column Name | Data Type | Description | | ------------------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | BLOCK_NUMBER | NUMBER | Also known as block height. The block number, which indicates the length of the blockchain, increases after the addition of each new block. | | BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The date and time at which the block was produced. | | TX_HASH | TEXT | Transaction hash is a unique 66-character identifier that is generated when a transaction is executed. | | TX_POSITION | NUMBER | The position of the transaction within the block. | | EVENT_INDEX | NUMBER | Event number within a transaction. | | CONTRACT_ADDRESS | TEXT | The address of the contract that the event log was emitted from. | | TOPICS | VARIANT | The un-decoded event input topics. | | TOPIC_0 | TEXT | The first topic of the event, which is a unique identifier for the event. | | TOPIC_1 | TEXT | The second topic of the event, if applicable. | | TOPIC_2 | TEXT | The third topic of the event, if applicable. | | TOPIC_3 | TEXT | The fourth topic of the event, if applicable. | | DATA | TEXT | The un-decoded event data. | | EVENT_REMOVED | BOOLEAN | Whether the event has been removed from the transaction. | | ORIGIN_FROM_ADDRESS | TEXT | The from address at the transaction level. | | ORIGIN_TO_ADDRESS | TEXT | The to address at the transaction level. | | ORIGIN_FUNCTION_SIGNATURE | TEXT | The function signature of the contract call that triggered this transaction. | | TX_SUCCEEDED | BOOLEAN | Whether the transaction was successful, returned as a boolean. | | EVENT_NAME | TEXT | The name of the event, as defined in the contract ABI. | | FULL_DECODED_LOG | VARIANT | The full decoded log, including the event name, the event parameters, and the data type of the event parameters. | | DECODED_LOG | OBJECT | The flattened decoded log, where the keys are the names of the event parameters, and the values are the values of the event parameters. | | CONTRACT_NAME | TEXT | The name of the contract, if the contract has a name() function. | | EZ_DECODED_EVENT_LOGS_ID | TEXT | The unique identifier for each row in the table. | | INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp at which the row was inserted into the table. | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp at which the row was last modified. | Was this page helpful? YesNo [Dim Labels](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels) [Ez Native Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers) ⌘I --- # Ez Native Transfers - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core EVM Ez Native Transfers [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers#columns) **Schema**: `flow.core_evm` **Table**: `ez_native_transfers` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers#description) Description ----------------------------------------------------------------------------------------------------------------- A curated and enriched table containing native token transfer events across EVM-compatible blockchains. This table consolidates native token (e.g., ETH, BNB, AVAX) transfer data from execution traces, providing a comprehensive view of all native token movements. The table includes enriched metadata such as USD values and transfer context, making it the primary source for native token transfer analysis. Each record represents a single native token transfer with complete context and enriched data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers#key-use-cases) Key Use Cases --------------------------------------------------------------------------------------------------------------------- * **Native Token Analysis**: Tracking native token movements and transfer patterns across EVM chains * **Value Flow Analysis**: Understanding how native tokens flow through the ecosystem * **Gas Economics**: Analyzing gas fee payments and native token usage for transaction costs * **Cross-Chain Native Analysis**: Comparing native token transfer patterns across different EVM-compatible blockchains * **User Behavior Analysis**: Understanding how users transfer native tokens for various purposes * **Network Economics**: Monitoring native token distribution and economic activity [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers#important-relationships) Important Relationships ----------------------------------------------------------------------------------------------------------------------------------------- * **core\_evm\_\_fact\_traces**: Links to underlying execution traces that generated these transfers * **core\_evm\_\_fact\_transactions**: Links to transactions that triggered these transfers * **core\_evm\_\_dim\_labels**: Links to address labels for user and contract identification * **price\_\_ez\_prices\_hourly**: Links to native token prices for USD value calculations * **core\_evm\_\_ez\_token\_transfers**: May provide comparison data with token transfers * **core\_\_ez\_token\_transfers**: May provide comparison data with native Flow transfers [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers#commonly-used-fields) Commonly-used Fields ----------------------------------------------------------------------------------------------------------------------------------- * **FROM\_ADDRESS/TO\_ADDRESS**: Essential for transfer flow analysis and user behavior studies * **AMOUNT/AMOUNT\_USD**: Important for transfer value analysis and economic activity tracking * **TYPE**: Critical for transfer type categorization and analysis * **TRACE\_INDEX**: Key for transfer ordering and execution sequence analysis * **TX\_HASH**: Essential for transaction linking and blockchain verification * **BLOCK\_TIMESTAMP**: Critical for time-series analysis and temporal transfer tracking [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers#columns) Columns --------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Also known as block height. The block number, which indicates the length of the blockchain, increases after the addition of each new block. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The date and time at which the block was produced. | | TX\_HASH | TEXT | Transaction hash is a unique 66-character identifier that is generated when a transaction is executed. | | TX\_POSITION | NUMBER | The position of the transaction within the block. | | TRACE\_INDEX | NUMBER | The index of the trace within the transaction. | | TRACE\_ADDRESS | TEXT | The trace address for this trace. | | TYPE | TEXT | The type of internal transaction. Common trace types are `CALL`, `DELEGATECALL`, and `STATICCALL`. | | FROM\_ADDRESS | TEXT | The sending address of this transfer. | | TO\_ADDRESS | TEXT | The receiving address of this transfer. This can be a contract address. | | AMOUNT | FLOAT | The decimal transformed amount for this token. Tokens without a decimal adjustment will be nulled out here. | | AMOUNT\_PRECISE\_RAW | TEXT | The amount of tokens transferred returned as a string to preserve precision. This value is not decimal adjusted. | | AMOUNT\_PRECISE | TEXT | The decimal transformed amount for this token returned as a string to preserve precision. Tokens without a decimal adjustment will be nulled out here. | | AMOUNT\_USD | FLOAT | Native asset value transferred, in USD. | | ORIGIN\_FROM\_ADDRESS | TEXT | The from address at the transaction level. | | ORIGIN\_TO\_ADDRESS | TEXT | The to address at the transaction level. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | The function signature of the call that triggered this transaction. | | EZ\_NATIVE\_TRANSFERS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was last modified. | Was this page helpful? YesNo [Ez Decoded Event Logs](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-decoded-event-logs) [Ez Token Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers) ⌘I --- # Ez Token Transfers - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core EVM Ez Token Transfers [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers#columns) **Schema**: `flow.core_evm` **Table**: `ez_token_transfers` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers#description) Description ---------------------------------------------------------------------------------------------------------------- A curated and enriched table containing token transfer events across EVM-compatible blockchains. This table consolidates token transfer data from event logs, providing a comprehensive view of all token movements including ERC-20, ERC-721, and other token standards. The table includes enriched metadata such as token names, symbols, decimals, and USD values, making it the primary source for token transfer analysis. Each record represents a single token transfer with complete context and enriched data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers#key-use-cases) Key Use Cases -------------------------------------------------------------------------------------------------------------------- * **Token Transfer Analysis**: Tracking token movements and transfer patterns across EVM chains * **Portfolio Tracking**: Monitoring token holdings and transfer activities for specific addresses * **Token Economics**: Analyzing token distribution, circulation, and economic activity * **DeFi Analysis**: Understanding token flows in DeFi protocols and yield farming activities * **Cross-Chain Token Analysis**: Comparing token transfer patterns across different EVM-compatible blockchains * **Token Performance**: Monitoring token usage, adoption, and transfer volume trends [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers#important-relationships) Important Relationships ---------------------------------------------------------------------------------------------------------------------------------------- * **core\_evm\_\_fact\_event\_logs**: Links to underlying event logs that generated these transfers * **core\_evm\_\_fact\_transactions**: Links to transactions that triggered these transfers * **core\_evm\_\_dim\_contracts**: Links to token contract metadata for transfer analysis * **core\_evm\_\_dim\_labels**: Links to address labels for user and contract identification * **price\_\_ez\_prices\_hourly**: Links to token prices for USD value calculations * **core\_\_ez\_token\_transfers**: May provide comparison data with native Flow token transfers [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers#commonly-used-fields) Commonly-used Fields ---------------------------------------------------------------------------------------------------------------------------------- * **FROM\_ADDRESS/TO\_ADDRESS**: Essential for transfer flow analysis and user behavior studies * **CONTRACT\_ADDRESS**: Critical for token identification and contract-specific analysis * **AMOUNT/AMOUNT\_USD**: Important for transfer value analysis and economic activity tracking * **TOKEN\_STANDARD**: Key for token type categorization and standard-specific analysis * **SYMBOL/NAME**: Critical for token identification and user interface display * **BLOCK\_TIMESTAMP**: Essential for time-series analysis and temporal transfer tracking [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers#columns) Columns -------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Also known as block height. The block number, which indicates the length of the blockchain, increases after the addition of each new block. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The date and time at which the block was produced. | | TX\_HASH | TEXT | Transaction hash is a unique 66-character identifier that is generated when a transaction is executed. | | TX\_POSITION | NUMBER | The position of the transaction within the block. | | EVENT\_INDEX | NUMBER | Event number within a transaction. | | FROM\_ADDRESS | TEXT | The sending address of this transfer. | | TO\_ADDRESS | TEXT | The receiving address of this transfer. This can be a contract address. | | CONTRACT\_ADDRESS | TEXT | The address of the contract that the event log was emitted from. | | TOKEN\_STANDARD | TEXT | The type of token transferred in this event, for example `erc721`, `erc1155`, or `erc20`. | | TOKEN\_IS\_VERIFIED | BOOLEAN | | | NAME | TEXT | The name of the deployed contract. Please note this is not necessarily unique. | | SYMBOL | TEXT | The symbol used to represent this contract. Please note this is not necessarily unique. | | DECIMALS | NUMBER | The decimals for the token contract. | | RAW\_AMOUNT\_PRECISE | TEXT | The amount of tokens transferred returned as a string to preserve precision. This value is not decimal adjusted. | | RAW\_AMOUNT | FLOAT | The amount of tokens transferred. This value is not decimal adjusted. | | AMOUNT\_PRECISE | TEXT | The decimal transformed amount for this token returned as a string to preserve precision. Tokens without a decimal adjustment will be nulled out here. | | AMOUNT | FLOAT | The decimal transformed amount for this token. Tokens without a decimal adjustment will be nulled out here. | | AMOUNT\_USD | FLOAT | The amount in US dollars for this transfer at the time of the transfer. Tokens without a decimal adjustment or price will be nulled out here. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | The function signature of the call that triggered this transaction. | | ORIGIN\_FROM\_ADDRESS | TEXT | The from address at the transaction level. | | ORIGIN\_TO\_ADDRESS | TEXT | The to address at the transaction level. | | EZ\_TOKEN\_TRANSFERS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was last modified. | Was this page helpful? YesNo [Ez Native Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers) [Fact Blocks](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks) ⌘I --- # Fact Blocks - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core EVM Fact Blocks [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks#columns) **Schema**: `flow.core_evm` **Table**: `fact_blocks` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks#description) Description --------------------------------------------------------------------------------------------------------- A comprehensive fact table containing block-level data for EVM-compatible blockchains. This table serves as the foundation for blockchain analysis, providing detailed information about each block including metadata, gas usage, mining information, and blockchain state. The table supports analysis of blockchain performance, gas economics, and network health across multiple EVM chains. Each record represents a single block with complete header information and aggregated transaction data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------- * **Blockchain Performance Analysis**: Monitoring block production rates, gas usage patterns, and network efficiency * **Gas Economics**: Analyzing gas prices, fee structures, and economic incentives across different EVM chains * **Network Health Monitoring**: Tracking block difficulty, mining rewards, and network security metrics * **Cross-Chain Comparison**: Comparing performance and characteristics across different EVM-compatible blockchains * **Mining Analysis**: Understanding validator/miner behavior and reward distribution patterns * **Blockchain State Tracking**: Monitoring blockchain progression and state changes over time [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks#important-relationships) Important Relationships --------------------------------------------------------------------------------------------------------------------------------- * **core\_evm\_\_fact\_transactions**: Links to transaction data within each block * **core\_evm\_\_fact\_event\_logs**: May link to event logs emitted in blocks * **core\_evm\_\_fact\_traces**: May link to execution traces for block analysis * **core\_\_fact\_blocks**: May provide comparison data with native Flow blocks * **price\_\_ez\_prices\_hourly**: May link to native token prices for economic analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks#commonly-used-fields) Commonly-used Fields --------------------------------------------------------------------------------------------------------------------------- * **BLOCK\_NUMBER**: Essential for block identification and chronological analysis * **BLOCK\_TIMESTAMP**: Critical for time-series analysis and temporal data aggregation * **GAS\_USED/GAS\_LIMIT**: Key for gas economics and network efficiency analysis * **TX\_COUNT**: Important for transaction volume and network activity analysis * **MINER**: Critical for mining analysis and validator behavior studies * **BASE\_FEE\_PER\_GAS**: Essential for EIP-1559 fee mechanism analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks#columns) Columns ------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Also known as block height. The block number, which indicates the length of the blockchain, increases after the addition of each new block. | | BLOCK\_HASH | TEXT | The hash of the block header for a given block. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The date and time at which the block was produced. | | NETWORK | TEXT | The network on the blockchain used by a transaction. | | TX\_COUNT | NUMBER | Total number of transactions within a block. | | SIZE | NUMBER | Block size, which is determined by a given block’s gas limit. | | MINER | TEXT | The address of the beneficiary to whom the mining rewards were given | | MIX\_HASH | TEXT | A string of a 256-bit hash encoded as a hexadecimal | | EXTRA\_DATA | TEXT | Any data included by the miner for a given block. | | PARENT\_HASH | TEXT | The hash of the block from which a given block is generated. Also known as the parent block. | | GAS\_USED | NUMBER | Total gas used in the block. | | GAS\_LIMIT | NUMBER | Total gas limit provided by all transactions in the block. | | BASE\_FEE\_PER\_GAS | NUMBER | A string of the base fee encoded in hexadecimal format. Please note that this response field will not be included in a block requested before the EIP-1559 upgrade | | DIFFICULTY | NUMBER | The effort required to mine the block. | | TOTAL\_DIFFICULTY | NUMBER | Total difficulty of the chain at a given block. | | SHA3\_UNCLES | TEXT | The mechanism which Ethereum Javascript RLP encodes an empty string. | | UNCLE\_BLOCKS | VARIANT | Uncle blocks occur when two blocks are mined and broadcasted at the same time, with the same block number. The block validated across the most nodes will be added to the primary chain, and the other one becomes an uncle block. Miners do receive rewards for uncle blocks. | | NONCE | NUMBER | Block nonce is a value used during mining to demonstrate proof of work for a given block. | | RECEIPTS\_ROOT | TEXT | The root of the state trie. | | STATE\_ROOT | TEXT | The root of the final state trie of the block | | TRANSACTIONS\_ROOT | TEXT | The root of the transaction trie of the block | | LOGS\_BLOOM | TEXT | The bloom filter for the logs of the block. | | FACT\_BLOCKS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was last modified. | Was this page helpful? YesNo [Ez Token Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers) [Fact Event Logs](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs) ⌘I --- # Fact Traces - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core EVM Fact Traces [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces#columns) **Schema**: `flow.core_evm` **Table**: `fact_traces` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces#description) Description --------------------------------------------------------------------------------------------------------- A comprehensive fact table containing execution trace data for transactions on EVM-compatible blockchains. This table provides detailed information about the internal execution of transactions, including contract calls, value transfers, and execution paths. The table supports deep transaction analysis, debugging, and understanding complex contract interactions across multiple EVM chains. Each record represents a single execution step with complete trace information and execution context. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------- * **Transaction Debugging**: Understanding why transactions failed or behaved unexpectedly * **Contract Interaction Analysis**: Tracking complex multi-contract interactions and call chains * **Value Flow Tracking**: Following native token and value transfers through complex transactions * **Gas Usage Analysis**: Understanding detailed gas consumption patterns in contract execution * **Security Analysis**: Identifying potential security issues and attack patterns * **Cross-Chain Trace Analysis**: Comparing execution patterns across different EVM-compatible blockchains [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces#important-relationships) Important Relationships --------------------------------------------------------------------------------------------------------------------------------- * **core\_evm\_\_fact\_transactions**: Links to transactions that generated these traces * **core\_evm\_\_fact\_blocks**: Links to blocks containing trace data * **core\_evm\_\_dim\_contracts**: Links to contract metadata for trace analysis * **core\_evm\_\_ez\_native\_transfers**: May link to curated native transfer events * **core\_evm\_\_fact\_event\_logs**: May link to events emitted during trace execution * **core\_\_fact\_transactions**: May provide comparison data with native Flow transactions [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces#commonly-used-fields) Commonly-used Fields --------------------------------------------------------------------------------------------------------------------------- * **TRACE\_INDEX**: Essential for trace ordering and execution sequence analysis * **FROM\_ADDRESS/TO\_ADDRESS**: Critical for call flow analysis and contract interaction tracking * **TYPE**: Important for trace categorization and execution type analysis * **VALUE**: Key for value transfer tracking and economic analysis * **GAS\_USED**: Critical for gas consumption analysis and optimization studies * **TRACE\_SUCCEEDED**: Essential for execution success analysis and error tracking [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces#columns) Columns ------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Also known as block height. The block number, which indicates the length of the blockchain, increases after the addition of each new block. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The date and time at which the block was produced. | | TX\_HASH | TEXT | Transaction hash is a unique 66-character identifier that is generated when a transaction is executed. | | TX\_POSITION | NUMBER | The position of the transaction within the block. | | TRACE\_INDEX | NUMBER | The index of the trace within the transaction. | | FROM\_ADDRESS | TEXT | The sending address of this transaction. | | TO\_ADDRESS | TEXT | The receiving address of this transaction. This can be a contract address. | | INPUT | TEXT | The input data for this trace. | | OUTPUT | TEXT | The output data for this trace. | | TYPE | TEXT | The type of internal transaction. Common trace types are `CALL`, `DELEGATECALL`, and `STATICCALL`. | | TRACE\_ADDRESS | TEXT | The trace address for this trace. | | SUB\_TRACES | NUMBER | The amount of nested sub traces for this trace. | | VALUE | FLOAT | The value transacted in the native asset. | | VALUE\_PRECISE\_RAW | TEXT | The precise, unadjusted amount of the transaction. This is returned as a string to avoid precision loss. | | VALUE\_PRECISE | TEXT | The precise, adjusted amount of the transaction. This is returned as a string to avoid precision loss. | | VALUE\_HEX | TEXT | The value of the transaction in hexadecimal format. | | GAS | NUMBER | The gas supplied for this trace. | | GAS\_USED | NUMBER | The gas used for this trace. | | ORIGIN\_FROM\_ADDRESS | TEXT | The sending address of this trace. This is not necessarily the from address of the transaction. | | ORIGIN\_TO\_ADDRESS | TEXT | The receiving address of this trace. This is not necessarily the to address of the transaction. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | The function signature of the contract call that triggered this transaction. | | TRACE\_SUCCEEDED | BOOLEAN | The boolean value representing if the trace succeeded. | | ERROR\_REASON | TEXT | The reason for the trace failure, if any. | | REVERT\_REASON | TEXT | The reason for the revert, if available. | | TX\_SUCCEEDED | BOOLEAN | Whether the transaction was successful, returned as a boolean. | | FACT\_TRACES\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was last modified. | Was this page helpful? YesNo [Fact Event Logs](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs) [Fact Transactions](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions) ⌘I --- # Fact Event Logs - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core EVM Fact Event Logs [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs#columns) **Schema**: `flow.core_evm` **Table**: `fact_event_logs` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs#description) Description ------------------------------------------------------------------------------------------------------------- A comprehensive fact table containing event log data emitted by smart contracts on EVM-compatible blockchains. This table serves as the foundation for smart contract analysis, providing detailed information about events including contract addresses, topics, data, and execution context. The table supports analysis of DeFi protocols, NFT marketplaces, and other smart contract applications across multiple EVM chains. Each record represents a single event log with complete emission details and metadata. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs#key-use-cases) Key Use Cases ----------------------------------------------------------------------------------------------------------------- * **Smart Contract Analysis**: Understanding contract behavior and event emission patterns * **DeFi Protocol Analysis**: Tracking DeFi events, swaps, liquidity changes, and yield farming activities * **NFT Analytics**: Monitoring NFT transfers, sales, and marketplace activities * **Event Tracking**: Following specific event types across different contracts and chains * **Contract Interaction Analysis**: Understanding how users interact with smart contracts * **Cross-Chain Event Analysis**: Comparing event patterns across different EVM-compatible blockchains [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------- * **core\_evm\_\_fact\_transactions**: Links to transactions that emitted these events * **core\_evm\_\_fact\_blocks**: Links to blocks containing event logs * **core\_evm\_\_dim\_contracts**: Links to contract metadata for event source identification * **core\_evm\_\_dim\_labels**: Links to address labels for contract and user identification * **core\_evm\_\_ez\_token\_transfers**: May link to curated token transfer events * **core\_\_fact\_events**: May provide comparison data with native Flow events [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------- * **CONTRACT\_ADDRESS**: Essential for contract identification and event source analysis * **TOPIC\_0**: Critical for event type identification and event categorization * **TOPICS**: Important for event parameter analysis and filtering * **DATA**: Key for event data extraction and parameter analysis * **TX\_HASH**: Essential for linking events to their originating transactions * **BLOCK\_TIMESTAMP**: Critical for time-series analysis and temporal event tracking [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs#columns) Columns ----------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Also known as block height. The block number, which indicates the length of the blockchain, increases after the addition of each new block. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The date and time at which the block was produced. | | TX\_HASH | TEXT | Transaction hash is a unique 66-character identifier that is generated when a transaction is executed. | | TX\_POSITION | NUMBER | The position of the transaction within the block. | | EVENT\_INDEX | NUMBER | Event number within a transaction. | | CONTRACT\_ADDRESS | TEXT | The address interacted with for a given event. | | TOPICS | VARIANT | The un-decoded event input topics. | | TOPIC\_0 | TEXT | The first topic of the event, which is a unique identifier for the event. | | TOPIC\_1 | TEXT | The second topic of the event, if applicable. | | TOPIC\_2 | TEXT | The third topic of the event, if applicable. | | TOPIC\_3 | TEXT | The fourth topic of the event, if applicable. | | DATA | TEXT | The un-decoded event data. | | EVENT\_REMOVED | BOOLEAN | Whether the event has been removed from the transaction. | | ORIGIN\_FROM\_ADDRESS | TEXT | The sending address of this transaction. | | ORIGIN\_TO\_ADDRESS | TEXT | The receiving address of this transaction. This can be a contract address. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | The function signature of the contract call that triggered this transaction. | | TX\_SUCCEEDED | BOOLEAN | Whether the transaction was successful, returned as a boolean. | | FACT\_EVENT\_LOGS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was last modified. | Was this page helpful? YesNo [Fact Blocks](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks) [Fact Traces](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces) ⌘I --- # Fact Transactions - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core EVM Fact Transactions [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions#columns) **Schema**: `flow.core_evm` **Table**: `fact_transactions` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions#description) Description --------------------------------------------------------------------------------------------------------------- A comprehensive fact table containing transaction-level data for EVM-compatible blockchains. This table serves as the primary source for transaction analysis, providing detailed information about each transaction including sender/receiver addresses, values, gas usage, fees, and execution status. The table supports analysis of transaction patterns, user behavior, and network activity across multiple EVM chains. Each record represents a single transaction with complete execution details and metadata. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------------- * **Transaction Analysis**: Tracking transaction volumes, success rates, and execution patterns * **User Behavior Analysis**: Understanding transaction patterns and user activity across EVM chains * **Gas Analysis**: Monitoring gas usage, fee structures, and transaction economics * **Cross-Chain Activity**: Comparing transaction patterns across different EVM-compatible blockchains * **Contract Interaction Analysis**: Understanding smart contract usage and interaction patterns * **Network Performance**: Monitoring transaction processing efficiency and network health [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions#important-relationships) Important Relationships --------------------------------------------------------------------------------------------------------------------------------------- * **core\_evm\_\_fact\_blocks**: Links to block data containing each transaction * **core\_evm\_\_fact\_event\_logs**: Links to event logs emitted by transactions * **core\_evm\_\_fact\_traces**: Links to execution traces for detailed transaction analysis * **core\_evm\_\_dim\_contracts**: Links to contract metadata for contract interactions * **core\_evm\_\_dim\_labels**: Links to address labels for user identification * **core\_\_fact\_transactions**: May provide comparison data with native Flow transactions [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions#commonly-used-fields) Commonly-used Fields --------------------------------------------------------------------------------------------------------------------------------- * **TX\_HASH**: Essential for transaction identification and blockchain verification * **FROM\_ADDRESS/TO\_ADDRESS**: Critical for transaction flow analysis and user behavior studies * **VALUE**: Important for transaction value analysis and economic activity tracking * **GAS\_USED/GAS\_PRICE**: Key for gas economics and transaction cost analysis * **TX\_SUCCEEDED**: Critical for success rate analysis and error tracking * **BLOCK\_TIMESTAMP**: Essential for time-series analysis and temporal data aggregation [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions#columns) Columns ------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Also known as block height. The block number, which indicates the length of the blockchain, increases after the addition of each new block. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The date and time at which the block was produced. | | TX\_HASH | TEXT | Transaction hash is a unique 66-character identifier that is generated when a transaction is executed. | | FROM\_ADDRESS | TEXT | The sending address of this transaction. | | TO\_ADDRESS | TEXT | The receiving address of this transaction. This can be a contract address. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | The function signature of the call that triggered this transaction. | | VALUE | FLOAT | The value transacted in the native asset. | | VALUE\_PRECISE\_RAW | TEXT | The precise, unadjusted amount of the transaction. This is returned as a string to avoid precision loss. | | VALUE\_PRECISE | TEXT | The precise, adjusted amount of the transaction. This is returned as a string to avoid precision loss. | | TX\_FEE | FLOAT | Amount paid to validate the transaction in the native asset. | | TX\_FEE\_PRECISE | TEXT | The precise amount of the transaction fee. This is returned as a string to avoid precision loss. | | TX\_SUCCEEDED | BOOLEAN | Whether the transaction was successful, returned as a boolean. | | TX\_TYPE | NUMBER | The type of transaction. | | NONCE | NUMBER | The number of transactions sent from a given address. | | TX\_POSITION | NUMBER | The position of the transaction within the block. | | INPUT\_DATA | TEXT | This column contains additional data for this transaction, and is commonly used as part of a contract interaction or as a message to the recipient. | | GAS\_PRICE | FLOAT | Cost per unit of gas in Gwei. | | GAS\_USED | NUMBER | Gas used by the transaction. | | GAS\_LIMIT | NUMBER | Maximum amount of gas allocated for the transaction. | | CUMULATIVE\_GAS\_USED | NUMBER | The total amount of gas used when this transaction was executed in the block. | | EFFECTIVE\_GAS\_PRICE | NUMBER | The total base charge plus tip paid for each unit of gas, in Gwei. | | MAX\_FEE\_PER\_GAS | FLOAT | The maximum fee per gas of the transaction, in Gwei. | | MAX\_PRIORITY\_FEE\_PER\_GAS | FLOAT | The maximum priority fee per gas of the transaction, in Gwei. | | Y\_PARITY | NUMBER | The y parity for the transaction. | | ACCESS\_LIST | VARIANT | The access list for the transaction. | | R | TEXT | The r value of the transaction signature. | | S | TEXT | The s value of the transaction signature. | | V | NUMBER | The v value of the transaction signature. | | FACT\_TRANSACTIONS\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp at which the row was last modified. | Was this page helpful? YesNo [Fact Traces](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces) [Defi](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/overview) ⌘I --- # Core Evm - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core EVM Core Evm [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/overview#overview) Overview ------------------------------------------------------------------------------------------------ This schema contains 10 tables and views for Flow data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/overview#tables-and-views) Tables and Views ---------------------------------------------------------------------------------------------------------------- [Dim Contract Abis\ -----------------\ \ This table contains the contract ABIs that we have sourced from Etherscan, the community, or bytecode matched.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contract-abis) [Dim Contracts\ -------------\ \ A dimensional table containing metadata for smart contracts deployed on EVM-compatible blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contracts) [Dim Labels\ ----------\ \ A dimensional table containing address labels and categorization data for EVM-compatible blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-labels) [Ez Decoded Event Logs\ ---------------------\ \ For information on how to submit a contract for decoding, as well as how ABIs are sourced, please visit here.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-decoded-event-logs) [Ez Native Transfers\ -------------------\ \ A curated and enriched table containing native token transfer events across EVM-compatible blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-native-transfers) [Ez Token Transfers\ ------------------\ \ A curated and enriched table containing token transfer events across EVM-compatible blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/ez-token-transfers) [Fact Blocks\ -----------\ \ A comprehensive fact table containing block-level data for EVM-compatible blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-blocks) [Fact Event Logs\ ---------------\ \ A comprehensive fact table containing event log data emitted by smart contracts on EVM-compatible blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-event-logs) [Fact Traces\ -----------\ \ A comprehensive fact table containing execution trace data for transactions on EVM-compatible blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-traces) [Fact Transactions\ -----------------\ \ A comprehensive fact table containing transaction-level data for EVM-compatible blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions) Was this page helpful? YesNo [Fact Transactions](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions) [Dim Contract Abis](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/dim-contract-abis) ⌘I --- # Dim Address Mapping - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Dim Address Mapping [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping#columns) **Schema**: `flow.core` **Table**: `dim_address_mapping` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping#description) Description ------------------------------------------------------------------------------------------------------------- This table maps EVM addresses to Flow addresses based on COA (Custody of Account) Creation events. Each row represents an association between a Flow address and an EVM address, enabling cross-chain identity mapping and analytics. A single Flow address may have multiple EVM addresses linked to it, reflecting multi-chain participation or asset bridging. The table is updated as new COA Creation events are detected on-chain. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping#key-use-cases) Key Use Cases ----------------------------------------------------------------------------------------------------------------- * Linking user or contract activity across Flow and EVM-compatible chains * Supporting cross-chain analytics, wallet attribution, and identity resolution * Enabling DeFi, NFT, and bridge analytics that require address mapping * Auditing and monitoring asset flows between Flow and EVM ecosystems [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------- * Can be joined to Flow transaction and event tables (e.g., `core.fact_transactions`, `core.fact_events`) via `FLOW_ADDRESS` for on-chain activity * Can be joined to EVM-based analytics tables via `EVM_ADDRESS` for cross-chain analysis * Used by curated models in DeFi and NFT domains to enrich user and contract analytics with cross-chain context [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------- * `FLOW_ADDRESS`: The Flow blockchain address for the user or contract * `EVM_ADDRESS`: The associated EVM-compatible address * `BLOCK_TIMESTAMP_ASSOCIATED`: Timestamp when the mapping was established * `BLOCK_HEIGHT_ASSOCIATED`: Block height at which the mapping was recorded [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping#columns) Columns ----------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_TIMESTAMP\_ASSOCIATED | TIMESTAMP\_NTZ | The timestamp (in UTC) when the block or transaction was recorded on the Flow blockchain. Data type: TIMESTAMP\_NTZ. This field is essential for time-series analysis, ordering events, and joining with other tables by time. For example, a block with block\_height 100,000 may have a block\_timestamp of ‘2023-01-01 12:00:00’. Used for analytics on network activity, transaction throughput, and historical state reconstruction. | | BLOCK\_HEIGHT\_ASSOCIATED | NUMBER | The block number, corresponds with height. | | FLOW\_ADDRESS | TEXT | The unique on-chain address representing an account or contract on the Flow blockchain. Data type: STRING. Addresses are used to identify participants, contracts, and assets in all Flow transactions and events. Example: ‘0x1cf0e2f2f715450’. Used for joins, analytics, and entity mapping. For more details, see [Flow Accounts and Addresses](https://developers.flow.com/build/basics/accounts)
. | | EVM\_ADDRESS | TEXT | The unique on-chain address representing an account or contract on the Flow blockchain. Data type: STRING. Addresses are used to identify participants, contracts, and assets in all Flow transactions and events. Example: ‘0x1cf0e2f2f715450’. Used for joins, analytics, and entity mapping. For more details, see [Flow Accounts and Addresses](https://developers.flow.com/build/basics/accounts)
. | | DIM\_ADDRESS\_MAPPING\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | Was this page helpful? YesNo [Core Tables](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/overview) [Dim Contract Labels](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels) ⌘I --- # Dim Contract Labels - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Dim Contract Labels [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels#columns) **Schema**: `flow.core` **Table**: `dim_contract_labels` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels#description) Description ------------------------------------------------------------------------------------------------------------- This table contains all contract labels referenced in the events of Flow transactions. Each row represents a unique contract, identified by its event contract address and contract name, and is enriched with account address metadata. The table provides a canonical mapping of contracts to their human-readable names and associated addresses, supporting entity resolution and contract-level analytics across the Flow blockchain. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels#key-use-cases) Key Use Cases ----------------------------------------------------------------------------------------------------------------- * Enriching event and transaction data with contract labels for analytics and dashboards * Supporting entity resolution and contract-level segmentation in DeFi, NFT, and governance analytics * Enabling contract-level filtering, grouping, and reporting in business intelligence tools * Auditing and monitoring contract activity and deployments on Flow [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------- * Can be joined to `core.fact_events` via `event_contract` to enrich event data with contract names and addresses * Can be joined to `core.fact_transactions` via contract addresses for transaction-level analytics * Used by curated gold models in DeFi, NFT, and other domains to provide contract context and labeling [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------- * `event_contract`: The Flow contract address emitting events * `contract_name`: The human-readable name of the contract * `account_address`: The account address associated with the contract [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels#columns) Columns ----------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | EVENT\_CONTRACT\_ID | TEXT | | | EVENT\_CONTRACT | TEXT | The Flow contract that emitted the event. Data type: STRING. This value is a concatenation of the contract’s account address and its primary name (e.g., ‘A.0ae53cb6e3f42a79.FlowToken’). Used for identifying the source of events, joining with contract metadata, and analyzing contract activity. Example: ‘A.0ae53cb6e3f42a79.FlowToken’. Equivalent to the ‘Contract’ column on Flowscan. | | CONTRACT\_NAME | TEXT | The primary name assigned to a smart contract on the Flow blockchain, typically derived from the contract’s deployment address. Data type: STRING. Used for identifying, filtering, and joining contract metadata. Example: ‘FlowToken’, ‘TopShot’. Important for contract-level analytics, entity mapping, and dashboarding. | | ACCOUNT\_ADDRESS | TEXT | The account address in 0x form that instantiated the contract called in the event. Note, on the Flow blockchain the account and the contract are separate as the account may have created more than one contract, in rare instances, such as the following FLOW address 0x8624b52f9ddcd04a. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | | DIM\_CONTRACT\_LABELS\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | Was this page helpful? YesNo [Dim Address Mapping](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping) [Dim Labels](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels) ⌘I --- # Dim Labels - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Dim Labels [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels#columns) **Schema**: `flow.core` **Table**: `dim_labels` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels#description) Description ---------------------------------------------------------------------------------------------------- This table provides a comprehensive mapping of Flow addresses to human-readable labels, supporting entity identification and classification across the blockchain. Each row represents a unique address and its associated label, with additional metadata such as label type, subtype, and creator. Labels are sourced from both automated algorithms and manual curation, enabling robust address classification for analytics and reporting. The table is continuously updated to reflect new addresses, protocol deployments, and community contributions. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels#key-use-cases) Key Use Cases -------------------------------------------------------------------------------------------------------- * Enriching transaction, event, and contract data with human-readable labels for dashboards and analytics * Segmenting addresses by type (e.g., CEX, DEX, dApp, game) and subtype (e.g., contract\_deployer, hot\_wallet) * Supporting compliance, risk analysis, and wallet attribution * Powering entity-level analytics for DeFi, NFT, and governance applications [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels#important-relationships) Important Relationships ---------------------------------------------------------------------------------------------------------------------------- * Can be joined to `core.fact_transactions`, `core.fact_events`, and other gold models via `address` for entity enrichment * Used by curated models in DeFi, NFT, and rewards domains to provide address context and segmentation * Label type and subtype fields enable advanced filtering and grouping in analytics workflows [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels#commonly-used-fields) Commonly-used Fields ---------------------------------------------------------------------------------------------------------------------- * `address`: The Flow blockchain address being labeled * `label`: The human-readable name or tag for the address * `label_type`: The primary category of the address (e.g., CEX, NFT, DeFi) * `label_subtype`: The secondary classification (e.g., hot\_wallet, validator) * `creator`: The source or contributor of the label [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels#columns) Columns -------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCKCHAIN | TEXT | The name of the blockchain network involved in the transaction or address. Data type: STRING. This field is used to distinguish between different blockchains (e.g., ‘flow’, ‘ethereum’, ‘polygon’) in cross-chain analytics, bridge activity, and multi-chain protocols. It is essential for filtering, aggregating, and attributing activity to the correct network, especially in bridge and DeFi models where assets may move between chains. Example: ‘flow’ for native Flow transactions, ‘ethereum’ for bridged assets. Important for cross-chain analytics, protocol attribution, and ensuring accurate data segmentation in multi-chain environments. | | CREATOR | TEXT | The source of the labeling information for the address. | | ADDRESS | TEXT | The unique on-chain address representing an account or contract on the Flow blockchain. Data type: STRING. Addresses are used to identify participants, contracts, and assets in all Flow transactions and events. Example: ‘0x1cf0e2f2f715450’. Used for joins, analytics, and entity mapping. For more details, see [Flow Accounts and Addresses](https://developers.flow.com/build/basics/accounts)
. | | ADDRESS\_NAME | TEXT | The name for a specific address, like Kraken or Huobi for CEX, or consensus vs verification for validator. | | LABEL\_TYPE | TEXT | The primary category or classification assigned to an address, contract, or entity (e.g., ‘CEX’, ‘Operator’, ‘NFT’, ‘DeFi’, ‘Game’). Data type: STRING. Used for grouping, filtering, and analyzing entities by type in dashboards and reports. Example: ‘CEX’ for centralized exchanges, ‘NFT’ for non-fungible token contracts. Important for segmentation and entity-level analytics. | | LABEL\_SUBTYPE | TEXT | A more granular classification within the primary `label_type`, specifying the role or function of the address or contract (e.g., ‘hot wallet’, ‘deposit wallet’, ‘validator’, ‘marketplace’). Data type: STRING. Used for detailed segmentation, filtering, and analytics. Example: ‘hot wallet’ under ‘CEX’, or ‘validator’ under ‘Operator’. Important for fine-grained entity analysis and reporting. | | LABEL | TEXT | A human-readable name or tag assigned to an address, contract, or entity for identification and analytics. Data type: STRING. Labels provide context such as project names, exchange names, or protocol identifiers. Used for dashboards, segmentation, and entity-level reporting. Example: ‘Blocto’, ‘NBA Top Shot’, ‘Flow Foundation’. Important for making blockchain data more interpretable and actionable. | | DIM\_LABELS\_ID | TEXT | A unique identifier for the record. In the context of blocks, this is the block hash—a cryptographic string that uniquely identifies a block on the Flow blockchain. Data type: STRING. Used for verifying block integrity, referencing blocks in other tables, and supporting chain reorganization analysis. Example: ‘a1b2c3d4…’. For other models, ‘id’ may refer to a unique row identifier. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Dim Contract Labels](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels) [Ez Token Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers) ⌘I --- # Ez Token Transfers - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Ez Token Transfers [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers#columns) **Schema**: `flow.core` **Table**: `ez_token_transfers` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers#description) Description ------------------------------------------------------------------------------------------------------------ This table records all token transfers on the Flow blockchain, capturing both native and fungible token movements between accounts. Each row represents a single transfer event, including metadata such as transaction ID, block height, timestamp, sender, recipient, token contract, and amount. The table provides a normalized, analytics-ready view of token flows, supporting financial analysis, wallet tracking, and protocol monitoring. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers#key-use-cases) Key Use Cases ---------------------------------------------------------------------------------------------------------------- * Analyzing token flow and wallet activity across the Flow ecosystem * Measuring protocol, dApp, or user-level token volumes and trends * Supporting DeFi analytics, whale tracking, and compliance monitoring * Building dashboards for token distribution, holder analysis, and transfer patterns [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------ * Derived from `core.fact_events` by extracting token transfer events and normalizing fields * Can be joined to `core.dim_labels` via `sender` or `recipient` for entity enrichment * Token contract field can be joined to contract label tables for protocol-level analytics * Used as a source for curated gold models in DeFi, rewards, and NFT analytics [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------ * `tx_id`: Unique identifier for the transaction containing the transfer * `sender`: The Flow address sending tokens * `recipient`: The Flow address receiving tokens * `token_contract`: The contract address of the transferred token * `amount`: The quantity of tokens transferred (decimal adjusted) * `block_timestamp`: Used for time-series and trend analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_HEIGHT | NUMBER | Block height is the unique, sequential integer assigned to each block as it is added to the Flow blockchain. It serves as the primary identifier for block ordering and is used to reference the position of a block within the chain. Data type: INTEGER. Block height is essential for joining block, transaction, and event tables, and for analyzing blockchain growth over time. For example, block height 100,000 refers to the 100,000th block produced on Flow. This field is critical for time-series analytics, chain reorganization analysis, and historical state reconstruction. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp (in UTC) when the block or transaction was recorded on the Flow blockchain. Data type: TIMESTAMP\_NTZ. This field is essential for time-series analysis, ordering events, and joining with other tables by time. For example, a block with block\_height 100,000 may have a block\_timestamp of ‘2023-01-01 12:00:00’. Used for analytics on network activity, transaction throughput, and historical state reconstruction. | | TX\_ID | TEXT | The unique identifier (hash) for a transaction on the Flow blockchain. Data type: STRING. Each transaction is assigned a cryptographic hash that ensures its uniqueness and immutability. Used for joining transaction data across tables, tracing transaction execution, and verifying transaction integrity. Example: ‘e3f1c2d4…’. Essential for transaction-level analytics, debugging, and cross-referencing with block and event data. | | SENDER | TEXT | Address sending the transferred token. | | RECIPIENT | TEXT | Address receiving the transferred token. | | TOKEN\_CONTRACT | TEXT | The Flow contract address for the token involved in the transaction. Data type: STRING. Used to identify the specific fungible or non-fungible token being transferred, swapped, or bridged. Example: ‘A.1654653399040a61.FlowToken’. Important for token-level analytics, filtering, and protocol attribution. | | AMOUNT | FLOAT | The quantity of points, tokens, or assets transferred in the transaction. Data type: NUMBER (decimal adjusted). This field represents the amount moved between accounts, earned through activities, or spent on rewards. Used for financial analysis, volume tracking, reward program analytics, and transaction value calculations. Example: 100.0 for 100 reward points, 50.5 for 50.5 Flow tokens. Critical for reward program performance analysis, user engagement tracking, and maintaining accurate transaction records. | | TX\_SUCCEEDED | BOOLEAN | Transaction status, if it succeeded or failed. | | EZ\_TOKEN\_TRANSFERS\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Dim Labels](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels) [Ez Transaction Actors](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors) ⌘I --- # Ez Transaction Actors - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Ez Transaction Actors [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors#columns) **Schema**: `flow.core` **Table**: `ez_transaction_actors` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors#description) Description --------------------------------------------------------------------------------------------------------------- This curated table extracts all addresses involved in the events of each transaction on the Flow blockchain, generating an array of distinct actors for every transaction. Actors include authorizers, payers, proposers, and any other addresses referenced in transaction events. The table provides a normalized, analytics-ready view of transaction participants, supporting entity-level analysis and wallet attribution. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------------- * Identifying all participants in a transaction for compliance and risk analysis * Supporting wallet attribution, entity mapping, and participant segmentation * Enabling analytics on transaction complexity, multi-sig usage, and collaborative workflows * Building dashboards for protocol, dApp, or user-level activity [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors#important-relationships) Important Relationships --------------------------------------------------------------------------------------------------------------------------------------- * Derived from `core.fact_transactions` and `core.fact_events` by extracting and aggregating participant addresses * Can be joined to `core.dim_labels` via `actors` for entity enrichment * Used by curated models in DeFi, NFT, and rewards domains to provide participant context [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors#commonly-used-fields) Commonly-used Fields --------------------------------------------------------------------------------------------------------------------------------- * `tx_id`: Unique identifier for the transaction * `actors`: Array of all addresses involved in the transaction (authorizers, payers, proposers, event participants) * `block_timestamp`: Used for time-series and participant trend analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors#columns) Columns ------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_HEIGHT | NUMBER | The block number, corresponds with height. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp (in UTC) when the block or transaction was recorded on the Flow blockchain. Data type: TIMESTAMP\_NTZ. This field is essential for time-series analysis, ordering events, and joining with other tables by time. For example, a block with block\_height 100,000 may have a block\_timestamp of ‘2023-01-01 12:00:00’. Used for analytics on network activity, transaction throughput, and historical state reconstruction. | | TX\_ID | TEXT | The unique identifier (hash) for a transaction on the Flow blockchain. Data type: STRING. Each transaction is assigned a cryptographic hash that ensures its uniqueness and immutability. Used for joining transaction data across tables, tracing transaction execution, and verifying transaction integrity. Example: ‘e3f1c2d4…’. Essential for transaction-level analytics, debugging, and cross-referencing with block and event data. | | ACTORS | ARRAY | An array of unique addresses involved in the events of a transaction, tagging them as actors in the transaction. | | PAYER | TEXT | | | PROPOSER | TEXT | | | AUTHORIZERS | ARRAY | | | TX\_SUCCEEDED | BOOLEAN | Transaction status, if it succeeded or failed. | | EZ\_TRANSACTION\_ACTORS\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Ez Token Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers) [Fact Account Storage](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-account-storage) ⌘I --- # Fact Blocks - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Blocks [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks#columns) **Schema**: `flow.core` **Table**: `fact_blocks` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks#description) Description ----------------------------------------------------------------------------------------------------- This table records all blocks produced on the Flow blockchain, capturing block-level metadata such as block height, timestamp, network, chain ID, transaction count, and parent block references. Each row represents a unique block, providing the foundational structure for all on-chain activity and supporting block-level analytics. The data is sourced directly from the Flow blockchain and is updated as new blocks are produced. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks#key-use-cases) Key Use Cases --------------------------------------------------------------------------------------------------------- * Analyzing block production rates and network performance * Measuring transaction throughput and block utilization * Investigating block-level events, forks, or anomalies * Supporting time-series analytics and historical blockchain state reconstruction * Serving as a join point for transaction, event, and token transfer models [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks#important-relationships) Important Relationships ----------------------------------------------------------------------------------------------------------------------------- * Serves as the parent table for `core.fact_transactions`, `core.fact_events`, and `core.ez_token_transfers`, which reference block height and block timestamp * Can be joined with `core__fact_transactions` on `block_height` to analyze transactions per block * Used by downstream models in the gold layer for time-based aggregations and network health metrics [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks#commonly-used-fields) Commonly-used Fields ----------------------------------------------------------------------------------------------------------------------- * `BLOCK_HEIGHT`: Unique identifier for each block, used for joins and ordering * `BLOCK_TIMESTAMP`: Timestamp of block production, essential for time-series analysis * `TX_COUNT`: Number of transactions included in the block, used for throughput and activity metrics * `CHAIN_ID`, `NETWORK`, `NETWORK_VERSION`: Identify the network context for the block * `PARENT_ID`: Reference to the parent block, useful for chain reorganization and lineage analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks#columns) Columns --------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_HEIGHT | NUMBER | Block height is the unique, sequential integer assigned to each block as it is added to the Flow blockchain. It serves as the primary identifier for block ordering and is used to reference the position of a block within the chain. Data type: INTEGER. Block height is essential for joining block, transaction, and event tables, and for analyzing blockchain growth over time. For example, block height 100,000 refers to the 100,000th block produced on Flow. This field is critical for time-series analytics, chain reorganization analysis, and historical state reconstruction. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp (in UTC) when the block or transaction was recorded on the Flow blockchain. Data type: TIMESTAMP\_NTZ. This field is essential for time-series analysis, ordering events, and joining with other tables by time. For example, a block with block\_height 100,000 may have a block\_timestamp of ‘2023-01-01 12:00:00’. Used for analytics on network activity, transaction throughput, and historical state reconstruction. | | NETWORK | TEXT | The name of the blockchain network where the block or transaction was recorded. Data type: STRING. For Flow, this typically indicates the environment (e.g., ‘mainnet’, ‘testnet’, ‘sandboxnet’). This field is important for distinguishing between production and test data, and for multi-network analytics. Example: ‘mainnet’. | | NETWORK\_VERSION | TEXT | The version identifier of the Flow blockchain network at the time the block was produced. Data type: STRING. This value changes when the network undergoes a protocol upgrade (“spork”). Useful for tracking changes in protocol behavior, analyzing the impact of upgrades, and debugging issues related to network versioning. Example: ‘spork-22’. For more information on Flow’s network upgrades (Sporks), see [https://developers.flow.com/nodes/node-operation/spork](https://developers.flow.com/nodes/node-operation/spork) | | CHAIN\_ID | TEXT | The unique identifier for the blockchain network (chain) where the block or transaction was recorded. Data type: STRING. On Flow, this value distinguishes between different network deployments (e.g., mainnet, testnet). Used for cross-network analytics and ensuring data integrity when working with multiple environments. Example: ‘flow-mainnet’ or ‘flow-testnet’. | | TX\_COUNT | NUMBER | The total number of transactions included in a given block on the Flow blockchain. Data type: INTEGER. This field is used to measure block utilization, analyze network throughput, and identify periods of high or low activity. For example, a block with tx\_count = 100 contains 100 transactions. Useful for performance monitoring and capacity planning. | | ID | TEXT | A unique identifier for the record. In the context of blocks, this is the block hash—a cryptographic string that uniquely identifies a block on the Flow blockchain. Data type: STRING. Used for verifying block integrity, referencing blocks in other tables, and supporting chain reorganization analysis. Example: ‘a1b2c3d4…’. For other models, ‘id’ may refer to a unique row identifier. | | PARENT\_ID | TEXT | The hash of the parent block for the current block on the Flow blockchain. Data type: STRING. This field establishes the chain structure by linking each block to its predecessor, enabling chain traversal and reorganization analysis. Example: ‘a1b2c3d4…’ (the block hash of the previous block). Used for lineage analysis, fork detection, and chain integrity verification. | | FACT\_BLOCKS\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | \_INSERTED\_TIMESTAMP | TIMESTAMP\_LTZ | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Fact Account Storage](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-account-storage) [Fact Events](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events) ⌘I --- # Fact Account Storage - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-account-storage#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Account Storage [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-account-storage#columns) **Schema**: `flow.core` **Table**: `fact_account_storage` **Type**: Base Table This table contains account storage data as of the last block each day. Please note that the table will only update once a day. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-account-storage#columns) Columns ------------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_HEIGHT | NUMBER | The block height of the last block for the day at which storage was fetched. | | ACCOUNT\_ADDRESS | TEXT | The address of the account for which storage was fetched. | | BLOCK\_DATE | DATE | The date for which storage was fetched at the last block of the day. | | ENCODED\_DATA | TEXT | The encoded data of the account storage. | | DECODED\_DATA | VARIANT | The decoded data of the account storage. | | STORAGE\_USED | NUMBER | The storage used by the account. | | STORAGE\_CAPACITY | NUMBER | The storage capacity of the account. | | FACT\_ACCOUNT\_STORAGE\_ID | TEXT | The surrogate key for the account storage. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp of that the row was inserted. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp of that the row was last modified. | Was this page helpful? YesNo [Ez Transaction Actors](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors) [Fact Blocks](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks) ⌘I --- # Core Tables - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Core Tables [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/overview#overview) Overview -------------------------------------------------------------------------------------------- This schema contains 9 tables and views for Flow data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/overview#tables-and-views) Tables and Views ------------------------------------------------------------------------------------------------------------ [Dim Address Mapping\ -------------------\ \ This table maps EVM addresses to Flow addresses based on COA (Custody of Account) Creation events.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping) [Dim Contract Labels\ -------------------\ \ This table contains all contract labels referenced in the events of Flow transactions.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-contract-labels) [Dim Labels\ ----------\ \ This table provides a comprehensive mapping of Flow addresses to human-readable labels, supporting entity identification and classification across …](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-labels) [Ez Token Transfers\ ------------------\ \ This table records all token transfers on the Flow blockchain, capturing both native and fungible token movements between accounts.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-token-transfers) [Ez Transaction Actors\ ---------------------\ \ This curated table extracts all addresses involved in the events of each transaction on the Flow blockchain, generating an array of distinct actors…](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/ez-transaction-actors) [Fact Account Storage\ --------------------\ \ This table contains account storage data as of the last block each day.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-account-storage) [Fact Blocks\ -----------\ \ This table records all blocks produced on the Flow blockchain, capturing block-level metadata such as block height, timestamp, network, chain ID, t…](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks) [Fact Events\ -----------\ \ This table records all events emitted by transactions on the Flow blockchain.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events) [Fact Transactions\ -----------------\ \ This table records all transactions executed on the Flow blockchain, including metadata such as transaction ID, block height, timestamp, proposer, …](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions) Was this page helpful? YesNo [Ez Moment Player Ids](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/ez-moment-player-ids) [Dim Address Mapping](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/dim-address-mapping) ⌘I --- # Fact Events - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Events [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events#columns) **Schema**: `flow.core` **Table**: `fact_events` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events#description) Description ----------------------------------------------------------------------------------------------------- This table records all events emitted by transactions on the Flow blockchain. Each row represents a single event, capturing metadata such as the transaction ID, block height, timestamp, event type, emitting contract, event index, and event data payload. The table provides a granular, event-level view of on-chain activity, supporting detailed event-driven analytics and contract monitoring. Data is sourced directly from Flow transaction execution and includes both user-defined and system events. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events#key-use-cases) Key Use Cases --------------------------------------------------------------------------------------------------------- * Analyzing contract activity and event emissions over time * Monitoring protocol-specific or user-defined events for dApps * Auditing on-chain activity and reconstructing transaction flows * Building dashboards for NFT, DeFi, and governance event tracking * Supporting alerting and anomaly detection based on event patterns [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events#important-relationships) Important Relationships ----------------------------------------------------------------------------------------------------------------------------- * Linked to `core.fact_blocks` via `block_height` and `block_timestamp` for block context * Linked to `core.fact_transactions` via `tx_id` for transaction context and execution results * Event contract and event type fields can be joined to `core.dim_contract_labels` and other label tables for entity enrichment * Used as a source for curated gold models in DeFi, NFT, and other domains that analyze event activity [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events#commonly-used-fields) Commonly-used Fields ----------------------------------------------------------------------------------------------------------------------- * `tx_id`: Unique identifier for the transaction emitting the event * `event_type`: Specifies the type of event (user-defined or system) * `event_contract`: Identifies the contract that emitted the event * `event_data`: Contains the event payload for analytics and business logic extraction * `block_timestamp`: Used for time-series analysis and event sequencing * `event_index`: Orders events within a transaction for accurate reconstruction [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events#columns) Columns --------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | TX\_ID | TEXT | The unique identifier (hash) for a transaction on the Flow blockchain. Data type: STRING. Each transaction is assigned a cryptographic hash that ensures its uniqueness and immutability. Used for joining transaction data across tables, tracing transaction execution, and verifying transaction integrity. Example: ‘e3f1c2d4…’. Essential for transaction-level analytics, debugging, and cross-referencing with block and event data. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp (in UTC) when the block or transaction was recorded on the Flow blockchain. Data type: TIMESTAMP\_NTZ. This field is essential for time-series analysis, ordering events, and joining with other tables by time. For example, a block with block\_height 100,000 may have a block\_timestamp of ‘2023-01-01 12:00:00’. Used for analytics on network activity, transaction throughput, and historical state reconstruction. | | BLOCK\_HEIGHT | NUMBER | Block height is the unique, sequential integer assigned to each block as it is added to the Flow blockchain. It serves as the primary identifier for block ordering and is used to reference the position of a block within the chain. Data type: INTEGER. Block height is essential for joining block, transaction, and event tables, and for analyzing blockchain growth over time. For example, block height 100,000 refers to the 100,000th block produced on Flow. This field is critical for time-series analytics, chain reorganization analysis, and historical state reconstruction. | | TX\_SUCCEEDED | BOOLEAN | Transaction status, if it succeeded or failed. | | EVENT\_INDEX | NUMBER | The zero-based position of the event within the list of events emitted by a transaction. Data type: INTEGER. This field indicates the order in which events occurred during transaction execution. Used for reconstructing event sequences, debugging, and analyzing event-driven workflows. Example: 0 (first event), 1 (second event), etc. Important for event ordering and traceability. | | EVENT\_CONTRACT | TEXT | The Flow contract that emitted the event. Data type: STRING. This value is a concatenation of the contract’s account address and its primary name (e.g., ‘A.0ae53cb6e3f42a79.FlowToken’). Used for identifying the source of events, joining with contract metadata, and analyzing contract activity. Example: ‘A.0ae53cb6e3f42a79.FlowToken’. Equivalent to the ‘Contract’ column on Flowscan. | | EVENT\_TYPE | TEXT | The name or identifier of the event emitted by a contract during transaction execution. Data type: STRING. In the `fact_events` table, this field represents the user-defined or system event type, such as ‘A.0ae53cb6e3f42a79.FlowToken.TokensDeposited’. Used for filtering, categorizing, and analyzing on-chain events. Example: ‘A.0ae53cb6e3f42a79.FlowToken.TokensWithdrawn’. For more details, see [Flow User-Defined Events](https://developers.flow.com/build/basics/events#user-defined-events)
. | | EVENT\_DATA | OBJECT | The data passed to the event, in the form of key-value pairs. | | FACT\_EVENTS\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | \_INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Fact Blocks](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-blocks) [Fact Transactions](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions) ⌘I --- # Fact Transactions - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Transactions [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions#columns) **Schema**: `flow.core` **Table**: `fact_transactions` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions#description) Description ----------------------------------------------------------------------------------------------------------- This table records all transactions executed on the Flow blockchain, including metadata such as transaction ID, block height, timestamp, proposer, payer, authorizers, gas limit, script, arguments, and execution results. Each row represents a unique transaction, capturing both successful and failed executions, and providing the foundation for transaction-level analytics and tracing. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions#key-use-cases) Key Use Cases --------------------------------------------------------------------------------------------------------------- * Analyzing transaction throughput and network activity * Investigating failed transactions and error messages * Tracing the flow of funds and contract interactions * Supporting DeFi, NFT, and governance analytics by linking transactions to events and token transfers * Building dashboards for transaction monitoring and user behavior analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions#important-relationships) Important Relationships ----------------------------------------------------------------------------------------------------------------------------------- * Linked to `core.fact_blocks` via `block_height` and `block_timestamp` for block-level context * Referenced by `core.fact_events` and `core.ez_token_transfers` for event and token transfer analysis * Used as a base for downstream gold models in DeFi, NFT, and governance analytics [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions#commonly-used-fields) Commonly-used Fields ----------------------------------------------------------------------------------------------------------------------------- * `TX_ID`: Unique identifier for each transaction, used for joins and tracing * `BLOCK_HEIGHT`, `BLOCK_TIMESTAMP`: Provide block context for the transaction * `PROPOSER`, `PAYER`, `AUTHORIZERS`: Identify the parties involved in the transaction * `TX_SUCCEEDED`, `ERROR_MSG`: Indicate transaction success or failure and error details * `GAS_LIMIT`: Specifies the maximum gas allowed for execution [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-transactions#columns) Columns --------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | TX\_ID | TEXT | The unique identifier (hash) for a transaction on the Flow blockchain. Data type: STRING. Each transaction is assigned a cryptographic hash that ensures its uniqueness and immutability. Used for joining transaction data across tables, tracing transaction execution, and verifying transaction integrity. Example: ‘e3f1c2d4…’. Essential for transaction-level analytics, debugging, and cross-referencing with block and event data. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp (in UTC) when the block or transaction was recorded on the Flow blockchain. Data type: TIMESTAMP\_NTZ. This field is essential for time-series analysis, ordering events, and joining with other tables by time. For example, a block with block\_height 100,000 may have a block\_timestamp of ‘2023-01-01 12:00:00’. Used for analytics on network activity, transaction throughput, and historical state reconstruction. | | BLOCK\_HEIGHT | NUMBER | Block height is the unique, sequential integer assigned to each block as it is added to the Flow blockchain. It serves as the primary identifier for block ordering and is used to reference the position of a block within the chain. Data type: INTEGER. Block height is essential for joining block, transaction, and event tables, and for analyzing blockchain growth over time. For example, block height 100,000 refers to the 100,000th block produced on Flow. This field is critical for time-series analytics, chain reorganization analysis, and historical state reconstruction. | | CHAIN\_ID | TEXT | The unique identifier for the blockchain network (chain) where the block or transaction was recorded. Data type: STRING. On Flow, this value distinguishes between different network deployments (e.g., mainnet, testnet). Used for cross-network analytics and ensuring data integrity when working with multiple environments. Example: ‘flow-mainnet’ or ‘flow-testnet’. | | PROPOSER | TEXT | The Flow address of the account that proposed the transaction. Data type: STRING. The proposer is responsible for submitting the transaction to the network and paying the proposal fee. This field is used to analyze transaction origination, proposer activity, and fee attribution. Example: ‘0x1cf0e2f2f715450’. Important for understanding transaction lifecycle and participant roles in Flow’s multi-signer model. | | PAYER | TEXT | The Flow address of the account responsible for paying the transaction fees. Data type: STRING. The payer may be different from the proposer or authorizers. This field is used to analyze fee attribution, sponsorship patterns, and participant roles in Flow’s multi-signer transaction model. Example: ‘0x1cf0e2f2f715450’. Important for understanding who bears the cost of transaction execution. | | AUTHORIZERS | ARRAY | A list of Flow addresses that authorized the transaction. Data type: ARRAY or STRING (comma-separated). Authorizers are accounts whose keys are required to sign the transaction, enabling multi-party authorization. This field is used to analyze participant roles, multi-sig patterns, and access control in Flow’s transaction model. Example: \[‘0x1cf0e2f2f715450’, ‘0x2a2e1b2c3d4e5f6’\]. Important for understanding transaction security and collaborative workflows. | | COUNT\_AUTHORIZERS | NUMBER | Number of authorizers | | GAS\_LIMIT | NUMBER | The maximum amount of computational resources (gas) allocated for executing the transaction on the Flow blockchain. Data type: INTEGER. If the transaction exceeds this limit, it will fail. This field is used to analyze resource usage, transaction costs, and execution constraints. Example: 1000. Important for understanding transaction execution, fee estimation, and optimizing smart contract operations. | | SCRIPT | TEXT | The Cadence smart contract code or script executed as part of the transaction. Data type: STRING. This field contains the source code that defines the transaction’s logic, including function calls, arguments, and contract interactions. Used for auditing, debugging, and analyzing smart contract usage on Flow. Example: a Cadence script for transferring tokens. For more details, see [Flow Cadence Scripts](https://developers.flow.com/tooling/fcl-js/scripts)
. | | ARGUMENTS | ARRAY | The parameters or values passed into the Cadence script when the transaction was submitted. Data type: ARRAY or STRING (JSON-encoded). Arguments customize the behavior of the script, enabling dynamic contract interactions. Used for auditing, debugging, and analyzing transaction intent. Example: \[‘0x1cf0e2f2f715450’, 100\]. Important for understanding how smart contracts are invoked and parameterized on Flow. | | TRANSACTION\_RESULT | OBJECT | The outcome of the transaction execution, including status (success/failure), error messages, and any events emitted. Data type: STRING (JSON-encoded or structured). This field is used to analyze transaction success rates, debug failures, and audit on-chain activity. Example: ‘`{"status": "success", "events": [...]}`’. Essential for understanding transaction lifecycle, error handling, and event-driven analytics on Flow. | | TX\_SUCCEEDED | BOOLEAN | Transaction status, if it succeeded or failed. | | ERROR\_MSG | TEXT | The error message associated with the transaction, if it failed. | | FACT\_TRANSACTIONS\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Fact Events](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/fact-events) [Core Evm](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/overview) ⌘I --- # Gov - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Gov Gov [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/overview#overview) Overview ------------------------------------------------------------------------------------------- This schema contains 2 tables and views for Flow data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/overview#tables-and-views) Tables and Views ----------------------------------------------------------------------------------------------------------- [Dim Validator Labels\ --------------------\ \ A dimensional table containing validator node metadata and labeling information for the Flow blockchain network.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels) [Ez Staking Actions\ ------------------\ \ A fact table containing transaction-level information on FLOW staking activities within the governance system.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions) Was this page helpful? YesNo [Fact Dex Swaps](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps) [Dim Validator Labels](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels) ⌘I --- # Dim Validator Labels - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Gov Dim Validator Labels [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels#columns) **Schema**: `flow.gov` **Table**: `dim_validator_labels` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels#description) Description ------------------------------------------------------------------------------------------------------------- A dimensional table containing validator node metadata and labeling information for the Flow blockchain network. This table serves as the foundation for understanding the validator ecosystem, providing information about node types, roles, and associated projects or organizations. It supports governance analysis by enabling identification and categorization of validator nodes based on their function in the consensus mechanism and their operational characteristics. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels#key-use-cases) Key Use Cases ----------------------------------------------------------------------------------------------------------------- * **Validator Identification**: Identifying and categorizing validator nodes by type and role in the network * **Governance Analysis**: Understanding the distribution of validator types and their impact on network security * **Network Architecture**: Analyzing the composition of the Flow blockchain’s multi-role validator system * **Project Attribution**: Identifying which organizations or projects operate specific validator nodes * **Staking Analysis**: Supporting staking operations by providing validator metadata for delegation decisions * **Network Health Monitoring**: Tracking validator distribution and identifying potential centralization risks [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------- * **gov\_\_ez\_staking\_actions**: Links to staking transactions involving these validator nodes * **core\_\_fact\_transactions**: May link to validator-related transactions for additional context * **core\_\_dim\_contract\_labels**: May provide additional labeling for validator contracts * **core\_\_fact\_events**: May link to validator-related events for governance analysis * **evm/core\_evm\_\_dim\_contracts**: For EVM-based validators, provides additional contract metadata [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------- * **NODE\_ID**: Primary identifier for validator nodes and staking operations * **VALIDATOR\_TYPE**: Essential for understanding validator roles and network architecture * **PROJECT\_NAME**: Important for governance transparency and validator operator identification [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels#columns) Columns ----------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | NODE\_ID | TEXT | The unique identifier for a validator node in the Flow blockchain network. Data type: STRING. This field represents the address or identifier of a validator node that participates in the consensus mechanism and staking operations. Used for validator identification, staking analysis, and governance operations. Example: ‘0x1234567890abcdef’ for a specific validator node address. Critical for staking operations, validator performance tracking, and maintaining the integrity of the Flow blockchain consensus mechanism. | | VALIDATOR\_TYPE | TEXT | The role or type of validator node in the Flow blockchain network. Data type: STRING. This field categorizes validator nodes based on their specific function in the consensus mechanism. Used for validator role analysis, network architecture understanding, and governance operations. Example: ‘consensus’ for consensus nodes, ‘execution’ for execution nodes, ‘collection’ for collection nodes, ‘verification’ for verification nodes, ‘access’ for access nodes. Critical for understanding Flow’s multi-role validator architecture, network performance analysis, and maintaining the distributed consensus mechanism. | | PROJECT\_NAME | TEXT | The overarching project or organization name associated with the validator node. Data type: STRING. This field provides a human-readable identifier for the entity operating the validator node, helping to categorize and identify validator operators. Used for validator operator analysis, governance transparency, and network participant identification. Example: ‘Kraken’ for Kraken-operated validators, ‘Dapper Labs’ for Dapper-operated validators. Critical for governance analysis, validator accountability, and understanding the distribution of network control among different entities. | Was this page helpful? YesNo [Gov](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/overview) [Ez Staking Actions](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions) ⌘I --- # Defi - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Defi [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/overview#overview) Overview -------------------------------------------------------------------------------------------- This schema contains 5 tables and views for Flow data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/overview#tables-and-views) Tables and Views ------------------------------------------------------------------------------------------------------------ [Dim Swap Pool Labels\ --------------------\ \ Models all DEX swap pool and pair creation events on the Flow blockchain.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels) [Ez Bridge Activity\ ------------------\ \ Enriched view of all token bridge transactions to and from the Flow blockchain, combining raw bridge activity with token symbol and USD price infor…](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity) [Ez Dex Swaps\ ------------\ \ Enriched view of all DEX swap transactions on the Flow blockchain, combining raw swap data with token symbol and USD price information.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps) [Fact Bridge Activity\ --------------------\ \ Records all token bridge transactions to and from the Flow blockchain using supported bridge protocols (e.g., Blocto Teleport, Celer Bridge).](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity) [Fact Dex Swaps\ --------------\ \ Records all decentralized exchange (DEX) swap transactions on the Flow blockchain.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps) Was this page helpful? YesNo [Fact Transactions](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/fact-transactions) [Dim Swap Pool Labels](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels) ⌘I --- # Ez Staking Actions - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Gov Ez Staking Actions [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [gov\_\_ez\_staking\_actions](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions#gov-ez-staking-actions) * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions#columns) **Schema**: `flow.gov` **Table**: `ez_staking_actions` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions#gov-ez-staking-actions) gov\_\_ez\_staking\_actions ====================================================================================================================================== [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions#description) Description ----------------------------------------------------------------------------------------------------------- A fact table containing transaction-level information on FLOW staking activities within the governance system. This table tracks all staking-related actions including delegation, undelegation, and reward collection operations. Each record represents a specific staking action with detailed metadata about the delegator, validator node, action type, and amount involved. The table serves as the primary source for staking analytics and governance participation analysis in the Flow ecosystem. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions#key-use-cases) Key Use Cases --------------------------------------------------------------------------------------------------------------- * **Staking Analysis**: Tracking delegation and undelegation patterns across the Flow network * **Governance Participation**: Understanding user engagement in the staking ecosystem * **Validator Performance**: Analyzing validator attractiveness and delegation trends * **Reward Distribution**: Monitoring staking rewards and their distribution patterns * **Network Security**: Understanding the distribution of staked FLOW and its impact on network security * **User Behavior Analysis**: Identifying patterns in how users interact with the staking system [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions#important-relationships) Important Relationships ----------------------------------------------------------------------------------------------------------------------------------- * **gov\_\_dim\_validator\_labels**: Links to validator metadata for node analysis and categorization * **core\_\_fact\_transactions**: Provides additional transaction context and blockchain data * **core\_\_fact\_events**: May link to staking-related events for detailed governance analysis * **core\_\_dim\_address\_mapping**: Provides additional user context for delegator analysis * **price\_\_ez\_prices\_hourly**: May link to FLOW price data for staking value analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions#commonly-used-fields) Commonly-used Fields ----------------------------------------------------------------------------------------------------------------------------- * **TX\_ID**: Primary identifier for linking to blockchain transactions and audit trails * **DELEGATOR**: User account address for delegator identification and behavior analysis * **NODE\_ID**: Validator node identifier for validator-specific analysis * **ACTION**: Staking operation type for transaction categorization and analysis * **AMOUNT**: Staking amount for value analysis and volume tracking * **BLOCK\_TIMESTAMP**: Temporal reference for chronological analysis and time-series tracking [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions#columns) Columns --------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | TX\_ID | TEXT | | | EVENT\_INDEX | NUMBER | | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | | | BLOCK\_HEIGHT | NUMBER | | | TX\_SUCCEEDED | BOOLEAN | | | DELEGATOR | TEXT | | | DELEGATOR\_ID | TEXT | | | ACTION | TEXT | | | AMOUNT | FLOAT | | | NODE\_ID | TEXT | | | EZ\_STAKING\_ACTIONS\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Dim Validator Labels](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/dim-validator-labels) [Nft](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/overview) ⌘I --- # Dim Swap Pool Labels - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Dim Swap Pool Labels [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels#columns) **Schema**: `flow.defi` **Table**: `dim_swap_pool_labels` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels#description) Description -------------------------------------------------------------------------------------------------------------- Models all DEX swap pool and pair creation events on the Flow blockchain. Captures metadata for each pool, including token contracts, deployment timestamp, pool ID, vault address, and swap contract. Supports pool-level analytics, liquidity tracking, and protocol attribution. Data is sourced from on-chain pool creation events and normalized for analytics. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------------ * Analyze DEX pool creation and liquidity provisioning * Attribute swaps to specific pools and protocols * Track pool deployment and vault addresses * Support liquidity, TVL, and protocol market share analysis * Power DeFi dashboards and pool explorer tools [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels#important-relationships) Important Relationships -------------------------------------------------------------------------------------------------------------------------------------- * Can be joined with `defi__fact_dex_swaps` and `defi__ez_dex_swaps` for swap-level analytics * Protocol attribution via `swap_contract` and `platform` fields * Token-level analytics via `token0_contract` and `token1_contract` [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels#commonly-used-fields) Commonly-used Fields -------------------------------------------------------------------------------------------------------------------------------- * `swap_contract`: DEX pool contract address * `deployment_timestamp`: When the pool was deployed * `token0_contract` / `token1_contract`: Token contracts in the pool * `pool_id`: Unique identifier for the pool * `vault_address`: Address holding pool assets [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels#columns) Columns ------------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | SWAP\_CONTRACT | TEXT | The smart contract address of the DEX swap pool or liquidity pool involved in the transaction. Data type: STRING. This field identifies the specific contract facilitating the swap, which is essential for protocol attribution, pool-level analytics, and tracing liquidity movements. For Metapier swaps, all pools may use the same master contract (e.g., ‘A.609e10301860b683.PierPair’), so the ‘pool\_id’ is required to differentiate between pools. Example: ‘A.609e10301860b683.PierPair’ for Metapier, or a unique contract address for other DEXs. Important for understanding liquidity routing, protocol usage, and swap path analysis. | | DEPLOYMENT\_TIMESTAMP | TIMESTAMP\_NTZ | The block timestamp from the deployment transaction. | | TOKEN0\_CONTRACT | TEXT | The contract for token0 in the swap pair. Positioning is determined by the order this token occurs in the Swap Contract creation transaction. | | TOKEN1\_CONTRACT | TEXT | The contract for token1 in the swap pair. Positioning is determined by the order this token occurs in the Swap Contract creation transaction. | | POOL\_ID | NUMBER | The ID of the swap pool, as designated by the DEX on contract creation. | | VAULT\_ADDRESS | TEXT | The account address that holds tokens on behalf of the swap contract. | | DIM\_SWAP\_POOL\_LABELS\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Defi](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/overview) [Ez Bridge Activity](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity) ⌘I --- # Ez Bridge Activity - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Ez Bridge Activity [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity#columns) **Schema**: `flow.defi` **Table**: `ez_bridge_activity` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity#description) Description ------------------------------------------------------------------------------------------------------------ Enriched view of all token bridge transactions to and from the Flow blockchain, combining raw bridge activity with token symbol and USD price information. Adds business logic for easier analytics, including normalized asset values and protocol attribution. Data is sourced from bridge events and joined with curated price feeds. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity#key-use-cases) Key Use Cases ---------------------------------------------------------------------------------------------------------------- * Analyze cross-chain token flows with USD normalization * Track protocol revenue and fee analytics in USD * Attribute bridge activity by token symbol and protocol * Power dashboards and user-facing analytics for cross-chain flows * Support compliance, risk, and DeFi market research [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------ * Sourced from `defi__fact_bridge_activity` (adds enrichment) * Joins with price models for USD values (`amount_usd`, `amount_fee_usd`) * Token symbol enrichment via curated price feeds * Can be joined with `core__ez_token_transfers` for full asset movement [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------ * `tx_id`: Unique transaction identifier for bridge event * `block_timestamp`: When the bridge transaction occurred * `token_symbol`: Abbreviated symbol for the bridged token * `amount`: Quantity of tokens bridged (decimal adjusted) * `amount_usd`: Value of tokens bridged in USD * `amount_fee_usd`: Fee charged by the bridge protocol in USD * `platform`: Name of the bridge protocol [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | TX\_ID | TEXT | The unique identifier (hash) for a transaction on the Flow blockchain. Data type: STRING. Each transaction is assigned a cryptographic hash that ensures its uniqueness and immutability. Used for joining transaction data across tables, tracing transaction execution, and verifying transaction integrity. Example: ‘e3f1c2d4…’. Essential for transaction-level analytics, debugging, and cross-referencing with block and event data. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp (in UTC) when the block or transaction was recorded on the Flow blockchain. Data type: TIMESTAMP\_NTZ. This field is essential for time-series analysis, ordering events, and joining with other tables by time. For example, a block with block\_height 100,000 may have a block\_timestamp of ‘2023-01-01 12:00:00’. Used for analytics on network activity, transaction throughput, and historical state reconstruction. | | BLOCK\_HEIGHT | NUMBER | Block height is the unique, sequential integer assigned to each block as it is added to the Flow blockchain. It serves as the primary identifier for block ordering and is used to reference the position of a block within the chain. Data type: INTEGER. Block height is essential for joining block, transaction, and event tables, and for analyzing blockchain growth over time. For example, block height 100,000 refers to the 100,000th block produced on Flow. This field is critical for time-series analytics, chain reorganization analysis, and historical state reconstruction. | | BRIDGE\_ADDRESS | TEXT | The Flow contract address for the bridge protocol used to transfer tokens to or from the Flow blockchain. Data type: STRING. Identifies the specific bridge (e.g., Blocto Teleport, Celer) facilitating cross-chain transfers. Used for protocol attribution, analytics, and filtering bridge activity. Example: ‘0xabcdef1234567890’. Important for cross-chain analytics and monitoring bridge usage. | | TOKEN\_ADDRESS | TEXT | The Flow contract address for the token involved in the transaction. Data type: STRING. Used to identify the specific fungible or non-fungible token being transferred, swapped, or bridged. Example: ‘A.1654653399040a61.FlowToken’. Important for token-level analytics, filtering, and protocol attribution. | | TOKEN\_SYMBOL | TEXT | Abbreviated symbol for the asset or token involved in the transaction. Data type: STRING. Used to quickly identify the type of asset (e.g., ‘FLOW’, ‘USDC’, ‘BLT’) in analytics, dashboards, and reporting. This field is essential for filtering, aggregating, and visualizing token-level activity, especially in bridge and DEX models. Example: ‘FLOW’ for Flow’s native token, ‘USDC’ for USD Coin. Important for token attribution, price lookups, and user-facing analytics. | | AMOUNT | FLOAT | The quantity of points, tokens, or assets transferred in the transaction. Data type: NUMBER (decimal adjusted). This field represents the amount moved between accounts, earned through activities, or spent on rewards. Used for financial analysis, volume tracking, reward program analytics, and transaction value calculations. Example: 100.0 for 100 reward points, 50.5 for 50.5 Flow tokens. Critical for reward program performance analysis, user engagement tracking, and maintaining accurate transaction records. | | AMOUNT\_FEE | FLOAT | The fee amount deducted by the protocol, bridge, or contract as part of the transaction. Data type: NUMBER (decimal adjusted). Represents the cost paid by the user for using the service (e.g., bridge fee). Example: 0.1 (for 0.1 Flow tokens). Used for fee analysis, cost tracking, and protocol revenue analytics. | | AMOUNT\_USD | FLOAT | The value of the amount field denominated in US dollars, based on available pricing data at the time of the transaction. Data type: NUMBER (decimal adjusted). Used for financial analysis, protocol revenue tracking, and cross-chain comparisons. Example: 100.25 (for $100.25 USD). This field is essential for normalizing value across different tokens and blockchains, enabling USD-based analytics and dashboards. Important for DeFi analytics, cost analysis, and protocol performance measurement. | | AMOUNT\_FEE\_USD | FLOAT | The value of the fee amount denominated in US dollars, based on available pricing data at the time of the transaction. Data type: NUMBER (decimal adjusted). Used for cost analysis, protocol revenue tracking, and financial reporting. Example: 0.25 (for $0.25 USD). Important for fee analytics and dashboards. | | SOURCE\_ADDRESS | TEXT | The Flow blockchain address of a wallet involved in the transaction (as sender, recipient, source, or destination). Data type: STRING. Used to identify participants in token transfers, swaps, or bridge activity. Example: ‘0x1cf0e2f2f715450’. Important for wallet attribution, cross-chain analytics, and user-level tracking. | | DESTINATION\_ADDRESS | TEXT | The Flow blockchain address of a wallet involved in the transaction (as sender, recipient, source, or destination). Data type: STRING. Used to identify participants in token transfers, swaps, or bridge activity. Example: ‘0x1cf0e2f2f715450’. Important for wallet attribution, cross-chain analytics, and user-level tracking. | | SOURCE\_CHAIN | TEXT | The name of the blockchain network involved in the transaction or address. Data type: STRING. This field is used to distinguish between different blockchains (e.g., ‘flow’, ‘ethereum’, ‘polygon’) in cross-chain analytics, bridge activity, and multi-chain protocols. It is essential for filtering, aggregating, and attributing activity to the correct network, especially in bridge and DeFi models where assets may move between chains. Example: ‘flow’ for native Flow transactions, ‘ethereum’ for bridged assets. Important for cross-chain analytics, protocol attribution, and ensuring accurate data segmentation in multi-chain environments. | | DESTINATION\_CHAIN | TEXT | The name of the blockchain network involved in the transaction or address. Data type: STRING. This field is used to distinguish between different blockchains (e.g., ‘flow’, ‘ethereum’, ‘polygon’) in cross-chain analytics, bridge activity, and multi-chain protocols. It is essential for filtering, aggregating, and attributing activity to the correct network, especially in bridge and DeFi models where assets may move between chains. Example: ‘flow’ for native Flow transactions, ‘ethereum’ for bridged assets. Important for cross-chain analytics, protocol attribution, and ensuring accurate data segmentation in multi-chain environments. | | PLATFORM | TEXT | The name of the bridge protocol or service used to transfer tokens or assets between blockchains. Data type: STRING. This field identifies the specific bridge (e.g., ‘blocto’, ‘celer’) facilitating the cross-chain transfer. Used for protocol attribution, analytics, and filtering bridge activity. Example: ‘blocto’ for Blocto Teleport, ‘celer’ for Celer Bridge. Important for cross-chain analytics, protocol usage tracking, and understanding the flow of assets between networks. | | EZ\_BRIDGE\_ACTIVITY\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Dim Swap Pool Labels](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/dim-swap-pool-labels) [Ez Dex Swaps](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps) ⌘I --- # Ez Dex Swaps - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Ez Dex Swaps [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps#columns) **Schema**: `flow.defi` **Table**: `ez_dex_swaps` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps#description) Description ------------------------------------------------------------------------------------------------------ Enriched view of all DEX swap transactions on the Flow blockchain, combining raw swap data with token symbol and USD price information. Adds business logic for easier analytics, including normalized asset values, protocol attribution, and swap path context. Data is sourced from swap events and joined with curated price feeds. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps#key-use-cases) Key Use Cases ---------------------------------------------------------------------------------------------------------- * Analyze DEX trading activity with USD normalization * Track protocol revenue and fee analytics in USD * Attribute swaps by token symbol, pool, and protocol * Power dashboards and user-facing analytics for DeFi trading * Support liquidity, slippage, and market research [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------ * Sourced from `defi__fact_dex_swaps` (adds enrichment) * Joins with price models for USD values (`amount_out_usd`, `amount_in_usd`) * Token symbol enrichment via curated price feeds * Can be joined with `defi__dim_swap_pool_labels` for pool metadata [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------ * `tx_id`: Unique transaction identifier for swap event * `block_timestamp`: When the swap occurred * `token_out_symbol` / `token_in_symbol`: Abbreviated symbols for swapped tokens * `amount_out_usd` / `amount_in_usd`: USD value of tokens swapped * `platform`: Name of the DEX protocol [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps#columns) Columns ---------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | TX\_ID | TEXT | The unique identifier (hash) for a transaction on the Flow blockchain. Data type: STRING. Each transaction is assigned a cryptographic hash that ensures its uniqueness and immutability. Used for joining transaction data across tables, tracing transaction execution, and verifying transaction integrity. Example: ‘e3f1c2d4…’. Essential for transaction-level analytics, debugging, and cross-referencing with block and event data. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp (in UTC) when the block or transaction was recorded on the Flow blockchain. Data type: TIMESTAMP\_NTZ. This field is essential for time-series analysis, ordering events, and joining with other tables by time. For example, a block with block\_height 100,000 may have a block\_timestamp of ‘2023-01-01 12:00:00’. Used for analytics on network activity, transaction throughput, and historical state reconstruction. | | BLOCK\_HEIGHT | NUMBER | Block height is the unique, sequential integer assigned to each block as it is added to the Flow blockchain. It serves as the primary identifier for block ordering and is used to reference the position of a block within the chain. Data type: INTEGER. Block height is essential for joining block, transaction, and event tables, and for analyzing blockchain growth over time. For example, block height 100,000 refers to the 100,000th block produced on Flow. This field is critical for time-series analytics, chain reorganization analysis, and historical state reconstruction. | | CONTRACT\_ADDRESS | TEXT | The smart contract address of the DEX swap pool or liquidity pool involved in the transaction. Data type: STRING. This field identifies the specific contract facilitating the swap, which is essential for protocol attribution, pool-level analytics, and tracing liquidity movements. For Metapier swaps, all pools may use the same master contract (e.g., ‘A.609e10301860b683.PierPair’), so the ‘pool\_id’ is required to differentiate between pools. Example: ‘A.609e10301860b683.PierPair’ for Metapier, or a unique contract address for other DEXs. Important for understanding liquidity routing, protocol usage, and swap path analysis. | | SWAP\_INDEX | NUMBER | The position of the swap within a transaction, indicating the order of execution in multi-hop or multi-pool swaps. Data type: NUMBER (integer). The first swap in a transaction is indexed at 0. If a transaction routes through multiple pools, each swap is assigned an incrementing index (e.g., 0, 1, 2). Used to reconstruct swap paths, analyze routing strategies, and understand complex DeFi trades. Example: A single-pool swap has swap\_index 0; a two-pool route has swaps with indices 0 and 1. Important for path analysis, DEX routing analytics, and multi-hop trade reconstruction. | | TRADER | TEXT | The account address of the trader performing the swap action. | | PLATFORM | TEXT | The name of the protocol, platform, or DEX where the event (swap, trade, or other DeFi action) occurred. Data type: STRING. Used to attribute activity to a specific protocol (e.g., ‘blocto’, ‘metapier’, ‘topshot\_marketplace’) for analytics, filtering, and reporting. This field is essential for protocol-level analysis, market share tracking, and understanding user behavior across DeFi platforms. Example: ‘blocto’ for BloctoSwap, ‘metapier’ for Metapier DEX. Important for protocol attribution, competitive analysis, and cross-platform comparisons. | | ORIGIN\_FROM\_ADDRESS | TEXT | The address from which the token is withdrawn (“token out”) in a DEX swap. Data type: STRING. For the first swap in a transaction, this is typically the trader’s address; for subsequent swaps in a multi-hop route, it may be a pool address. Used to trace token flow and participant roles in swaps. Example: ‘0x1cf0e2f2f715450’ (trader) or a pool address for later hops. Important for swap path analysis and wallet attribution. | | TOKEN\_OUT | TEXT | The smart contract address for the token being swapped out of the trader’s wallet (or previous pool) in a DEX swap. Data type: STRING. Used to identify the specific token being sent out, supporting token-level analytics and swap path tracing. Example: ‘A.1654653399040a61.FlowToken’. Directionality is always from the trader to the pool or next hop in multi-pool swaps. | | TOKEN\_OUT\_SYMBOL | TEXT | Short-name symbol for the crypto token or asset, such as ‘FLOW’, ‘USDC’, or ‘BLT’. Data type: STRING. Used to identify the asset in analytics, dashboards, and reporting. This field is critical for token-level analysis, price lookups, and filtering. Example: ‘FLOW’ for Flow’s native token, ‘USDC’ for USD Coin. Important for user-facing analytics, protocol attribution, and cross-chain comparisons. | | AMOUNT\_OUT | FLOAT | The amount of tokens sent out from the trader’s wallet (or previous pool) in a DEX swap. Data type: NUMBER (decimal adjusted). Represents the quantity of the “out” token in the swap, from the trader’s perspective. Used for volume analysis, price impact, and swap path tracing. Example: 50.0 (for 50 tokens swapped out). Directionality is always from the trader to the pool or next hop in multi-pool swaps. | | AMOUNT\_OUT\_USD | FLOAT | The value of the amount field denominated in US dollars, based on available pricing data at the time of the transaction. Data type: NUMBER (decimal adjusted). Used for financial analysis, protocol revenue tracking, and cross-chain comparisons. Example: 100.25 (for $100.25 USD). This field is essential for normalizing value across different tokens and blockchains, enabling USD-based analytics and dashboards. Important for DeFi analytics, cost analysis, and protocol performance measurement. | | ORIGIN\_TO\_ADDRESS | TEXT | The address receiving the token being swapped in (“token in”) during a DEX swap. Data type: STRING. For the initial deposit, this is typically the pool address; for the final swap, it is usually the trader’s address. Used to trace token flow, swap completion, and participant roles. Example: pool address for intermediate hops, trader address for final destination. Important for swap path analysis and wallet attribution. | | TOKEN\_IN | TEXT | The smart contract address for the token that is being swapped into the traders wallet. | | Token OUT / IN is from the perspective of the trader. So, an out token is leaving the wallet while the in token is being deposited to the wallet. This perspective is not changing for multi-pool trades - think of it directionally, the tokens continue flowing from out to in. Out of wallet, into pool, out of pool, into (another pool / wallet), with the final movement being tokens into final wallet. | | | | TOKEN\_IN\_SYMBOL | TEXT | Short-name symbol for the crypto token or asset, such as ‘FLOW’, ‘USDC’, or ‘BLT’. Data type: STRING. Used to identify the asset in analytics, dashboards, and reporting. This field is critical for token-level analysis, price lookups, and filtering. Example: ‘FLOW’ for Flow’s native token, ‘USDC’ for USD Coin. Important for user-facing analytics, protocol attribution, and cross-chain comparisons. | | AMOUNT\_IN | FLOAT | The amount of tokens received by the trader (or next pool) in a DEX swap. Data type: NUMBER (decimal adjusted). Represents the quantity of the “in” token in the swap, from the trader’s perspective. Used for volume analysis, price impact, and swap path tracing. Example: 49.5 (for 49.5 tokens received). Directionality is always from the pool to the trader or next hop in multi-pool swaps. | | AMOUNT\_IN\_USD | FLOAT | The value of the amount field denominated in US dollars, based on available pricing data at the time of the transaction. Data type: NUMBER (decimal adjusted). Used for financial analysis, protocol revenue tracking, and cross-chain comparisons. Example: 100.25 (for $100.25 USD). This field is essential for normalizing value across different tokens and blockchains, enabling USD-based analytics and dashboards. Important for DeFi analytics, cost analysis, and protocol performance measurement. | | EZ\_DEX\_SWAPS\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Ez Bridge Activity](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-bridge-activity) [Fact Bridge Activity](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity) ⌘I --- # Fact Bridge Activity - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Fact Bridge Activity [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity#columns) **Schema**: `flow.defi` **Table**: `fact_bridge_activity` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity#description) Description -------------------------------------------------------------------------------------------------------------- Records all token bridge transactions to and from the Flow blockchain using supported bridge protocols (e.g., Blocto Teleport, Celer Bridge). Captures the full context of each cross-chain transfer, including source/destination addresses, token details, amounts, fees, and protocol metadata. Data is sourced from on-chain bridge events and normalized for analytics. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------------ * Analyze cross-chain token flows into and out of Flow * Monitor bridge usage, volume, and protocol adoption * Track user participation in bridging activity * Attribute fees and bridge revenue by protocol * Support compliance and risk monitoring for cross-chain transfers [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity#important-relationships) Important Relationships -------------------------------------------------------------------------------------------------------------------------------------- * Linked to `defi__ez_bridge_activity` for enriched analytics (adds token symbols, USD values) * Can be joined with `core__ez_token_transfers` for end-to-end asset movement * Protocol attribution via `platform` and `bridge_address` fields * Token-level analytics via `token_address` and `amount` [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity#commonly-used-fields) Commonly-used Fields -------------------------------------------------------------------------------------------------------------------------------- * `tx_id`: Unique transaction identifier for bridge event * `block_timestamp`: When the bridge transaction occurred * `bridge_address`: Contract address of the bridge protocol * `token_address`: Contract address of the bridged token * `amount`: Quantity of tokens bridged (decimal adjusted) * `amount_fee`: Fee charged by the bridge protocol * `source_chain` / `destination_chain`: Blockchains involved in the transfer * `platform`: Name of the bridge protocol [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity#columns) Columns ------------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | TX\_ID | TEXT | The unique identifier (hash) for a transaction on the Flow blockchain. Data type: STRING. Each transaction is assigned a cryptographic hash that ensures its uniqueness and immutability. Used for joining transaction data across tables, tracing transaction execution, and verifying transaction integrity. Example: ‘e3f1c2d4…’. Essential for transaction-level analytics, debugging, and cross-referencing with block and event data. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp (in UTC) when the block or transaction was recorded on the Flow blockchain. Data type: TIMESTAMP\_NTZ. This field is essential for time-series analysis, ordering events, and joining with other tables by time. For example, a block with block\_height 100,000 may have a block\_timestamp of ‘2023-01-01 12:00:00’. Used for analytics on network activity, transaction throughput, and historical state reconstruction. | | BLOCK\_HEIGHT | NUMBER | Block height is the unique, sequential integer assigned to each block as it is added to the Flow blockchain. It serves as the primary identifier for block ordering and is used to reference the position of a block within the chain. Data type: INTEGER. Block height is essential for joining block, transaction, and event tables, and for analyzing blockchain growth over time. For example, block height 100,000 refers to the 100,000th block produced on Flow. This field is critical for time-series analytics, chain reorganization analysis, and historical state reconstruction. | | BRIDGE\_ADDRESS | TEXT | The Flow contract address for the bridge protocol used to transfer tokens to or from the Flow blockchain. Data type: STRING. Identifies the specific bridge (e.g., Blocto Teleport, Celer) facilitating cross-chain transfers. Used for protocol attribution, analytics, and filtering bridge activity. Example: ‘0xabcdef1234567890’. Important for cross-chain analytics and monitoring bridge usage. | | TOKEN\_ADDRESS | TEXT | The Flow contract address for the token involved in the transaction. Data type: STRING. Used to identify the specific fungible or non-fungible token being transferred, swapped, or bridged. Example: ‘A.1654653399040a61.FlowToken’. Important for token-level analytics, filtering, and protocol attribution. | | AMOUNT | FLOAT | The quantity of points, tokens, or assets transferred in the transaction. Data type: NUMBER (decimal adjusted). This field represents the amount moved between accounts, earned through activities, or spent on rewards. Used for financial analysis, volume tracking, reward program analytics, and transaction value calculations. Example: 100.0 for 100 reward points, 50.5 for 50.5 Flow tokens. Critical for reward program performance analysis, user engagement tracking, and maintaining accurate transaction records. | | AMOUNT\_FEE | FLOAT | The fee amount deducted by the protocol, bridge, or contract as part of the transaction. Data type: NUMBER (decimal adjusted). Represents the cost paid by the user for using the service (e.g., bridge fee). Example: 0.1 (for 0.1 Flow tokens). Used for fee analysis, cost tracking, and protocol revenue analytics. | | SOURCE\_ADDRESS | TEXT | The Flow blockchain address of a wallet involved in the transaction (as sender, recipient, source, or destination). Data type: STRING. Used to identify participants in token transfers, swaps, or bridge activity. Example: ‘0x1cf0e2f2f715450’. Important for wallet attribution, cross-chain analytics, and user-level tracking. | | DESTINATION\_ADDRESS | TEXT | The Flow blockchain address of a wallet involved in the transaction (as sender, recipient, source, or destination). Data type: STRING. Used to identify participants in token transfers, swaps, or bridge activity. Example: ‘0x1cf0e2f2f715450’. Important for wallet attribution, cross-chain analytics, and user-level tracking. | | SOURCE\_CHAIN | TEXT | The name of the blockchain network involved in the transaction or address. Data type: STRING. This field is used to distinguish between different blockchains (e.g., ‘flow’, ‘ethereum’, ‘polygon’) in cross-chain analytics, bridge activity, and multi-chain protocols. It is essential for filtering, aggregating, and attributing activity to the correct network, especially in bridge and DeFi models where assets may move between chains. Example: ‘flow’ for native Flow transactions, ‘ethereum’ for bridged assets. Important for cross-chain analytics, protocol attribution, and ensuring accurate data segmentation in multi-chain environments. | | DESTINATION\_CHAIN | TEXT | The name of the blockchain network involved in the transaction or address. Data type: STRING. This field is used to distinguish between different blockchains (e.g., ‘flow’, ‘ethereum’, ‘polygon’) in cross-chain analytics, bridge activity, and multi-chain protocols. It is essential for filtering, aggregating, and attributing activity to the correct network, especially in bridge and DeFi models where assets may move between chains. Example: ‘flow’ for native Flow transactions, ‘ethereum’ for bridged assets. Important for cross-chain analytics, protocol attribution, and ensuring accurate data segmentation in multi-chain environments. | | PLATFORM | TEXT | The name of the bridge protocol or service used to transfer tokens or assets between blockchains. Data type: STRING. This field identifies the specific bridge (e.g., ‘blocto’, ‘celer’) facilitating the cross-chain transfer. Used for protocol attribution, analytics, and filtering bridge activity. Example: ‘blocto’ for Blocto Teleport, ‘celer’ for Celer Bridge. Important for cross-chain analytics, protocol usage tracking, and understanding the flow of assets between networks. | | FACT\_BRIDGE\_ACTIVITY\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Ez Dex Swaps](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/ez-dex-swaps) [Fact Dex Swaps](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps) ⌘I --- # Fact Dex Swaps - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Fact Dex Swaps [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps#columns) **Schema**: `flow.defi` **Table**: `fact_dex_swaps` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps#description) Description -------------------------------------------------------------------------------------------------------- Records all decentralized exchange (DEX) swap transactions on the Flow blockchain. Captures the full context of each swap, including trader, pool, token in/out, amounts, and protocol metadata. Data is sourced from on-chain swap events and normalized for analytics, supporting both single-pool and multi-hop swaps. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------ * Analyze DEX trading activity and swap volume * Track user participation and trading behavior * Attribute swaps to specific pools and protocols * Support price impact, slippage, and liquidity analysis * Power DeFi dashboards and market research [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps#important-relationships) Important Relationships -------------------------------------------------------------------------------------------------------------------------------- * Linked to `defi__ez_dex_swaps` for enriched analytics (adds token symbols, USD values) * Can be joined with `defi__dim_swap_pool_labels` for pool metadata * Protocol attribution via `platform` and `contract_address` fields * Token-level analytics via `token_in`/`token_out` and amounts [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps#commonly-used-fields) Commonly-used Fields -------------------------------------------------------------------------------------------------------------------------- * `tx_id`: Unique transaction identifier for swap event * `block_timestamp`: When the swap occurred * `contract_address`: DEX pool contract address * `swap_index`: Order of swap in multi-hop transactions * `trader`: Account address of the swap initiator * `token_out` / `token_in`: Token contract addresses swapped out/in * `amount_out` / `amount_in`: Amounts swapped (decimal adjusted) * `platform`: Name of the DEX protocol [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-dex-swaps#columns) Columns ------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | TX\_ID | TEXT | The unique identifier (hash) for a transaction on the Flow blockchain. Data type: STRING. Each transaction is assigned a cryptographic hash that ensures its uniqueness and immutability. Used for joining transaction data across tables, tracing transaction execution, and verifying transaction integrity. Example: ‘e3f1c2d4…’. Essential for transaction-level analytics, debugging, and cross-referencing with block and event data. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp (in UTC) when the block or transaction was recorded on the Flow blockchain. Data type: TIMESTAMP\_NTZ. This field is essential for time-series analysis, ordering events, and joining with other tables by time. For example, a block with block\_height 100,000 may have a block\_timestamp of ‘2023-01-01 12:00:00’. Used for analytics on network activity, transaction throughput, and historical state reconstruction. | | BLOCK\_HEIGHT | NUMBER | Block height is the unique, sequential integer assigned to each block as it is added to the Flow blockchain. It serves as the primary identifier for block ordering and is used to reference the position of a block within the chain. Data type: INTEGER. Block height is essential for joining block, transaction, and event tables, and for analyzing blockchain growth over time. For example, block height 100,000 refers to the 100,000th block produced on Flow. This field is critical for time-series analytics, chain reorganization analysis, and historical state reconstruction. | | CONTRACT\_ADDRESS | TEXT | The smart contract address of the DEX swap pool or liquidity pool involved in the transaction. Data type: STRING. This field identifies the specific contract facilitating the swap, which is essential for protocol attribution, pool-level analytics, and tracing liquidity movements. For Metapier swaps, all pools may use the same master contract (e.g., ‘A.609e10301860b683.PierPair’), so the ‘pool\_id’ is required to differentiate between pools. Example: ‘A.609e10301860b683.PierPair’ for Metapier, or a unique contract address for other DEXs. Important for understanding liquidity routing, protocol usage, and swap path analysis. | | SWAP\_INDEX | NUMBER | The position of the swap within a transaction, indicating the order of execution in multi-hop or multi-pool swaps. Data type: NUMBER (integer). The first swap in a transaction is indexed at 0. If a transaction routes through multiple pools, each swap is assigned an incrementing index (e.g., 0, 1, 2). Used to reconstruct swap paths, analyze routing strategies, and understand complex DeFi trades. Example: A single-pool swap has swap\_index 0; a two-pool route has swaps with indices 0 and 1. Important for path analysis, DEX routing analytics, and multi-hop trade reconstruction. | | TRADER | TEXT | The account address of the trader performing the swap action. | | PLATFORM | TEXT | The name of the protocol, platform, or DEX where the event (swap, trade, or other DeFi action) occurred. Data type: STRING. Used to attribute activity to a specific protocol (e.g., ‘blocto’, ‘metapier’, ‘topshot\_marketplace’) for analytics, filtering, and reporting. This field is essential for protocol-level analysis, market share tracking, and understanding user behavior across DeFi platforms. Example: ‘blocto’ for BloctoSwap, ‘metapier’ for Metapier DEX. Important for protocol attribution, competitive analysis, and cross-platform comparisons. | | ORIGIN\_FROM\_ADDRESS | TEXT | The address from which the token is withdrawn (“token out”) in a DEX swap. Data type: STRING. For the first swap in a transaction, this is typically the trader’s address; for subsequent swaps in a multi-hop route, it may be a pool address. Used to trace token flow and participant roles in swaps. Example: ‘0x1cf0e2f2f715450’ (trader) or a pool address for later hops. Important for swap path analysis and wallet attribution. | | TOKEN\_OUT | TEXT | The smart contract address for the token being swapped out of the trader’s wallet (or previous pool) in a DEX swap. Data type: STRING. Used to identify the specific token being sent out, supporting token-level analytics and swap path tracing. Example: ‘A.1654653399040a61.FlowToken’. Directionality is always from the trader to the pool or next hop in multi-pool swaps. | | AMOUNT\_OUT | FLOAT | The amount of tokens sent out from the trader’s wallet (or previous pool) in a DEX swap. Data type: NUMBER (decimal adjusted). Represents the quantity of the “out” token in the swap, from the trader’s perspective. Used for volume analysis, price impact, and swap path tracing. Example: 50.0 (for 50 tokens swapped out). Directionality is always from the trader to the pool or next hop in multi-pool swaps. | | ORIGIN\_TO\_ADDRESS | TEXT | The address receiving the token being swapped in (“token in”) during a DEX swap. Data type: STRING. For the initial deposit, this is typically the pool address; for the final swap, it is usually the trader’s address. Used to trace token flow, swap completion, and participant roles. Example: pool address for intermediate hops, trader address for final destination. Important for swap path analysis and wallet attribution. | | TOKEN\_IN | TEXT | The smart contract address for the token that is being swapped into the traders wallet. | | Token OUT / IN is from the perspective of the trader. So, an out token is leaving the wallet while the in token is being deposited to the wallet. This perspective is not changing for multi-pool trades - think of it directionally, the tokens continue flowing from out to in. Out of wallet, into pool, out of pool, into (another pool / wallet), with the final movement being tokens into final wallet. | | | | AMOUNT\_IN | FLOAT | The amount of tokens received by the trader (or next pool) in a DEX swap. Data type: NUMBER (decimal adjusted). Represents the quantity of the “in” token in the swap, from the trader’s perspective. Used for volume analysis, price impact, and swap path tracing. Example: 49.5 (for 49.5 tokens received). Directionality is always from the pool to the trader or next hop in multi-pool swaps. | | FACT\_DEX\_SWAPS\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Fact Bridge Activity](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/fact-bridge-activity) [Gov](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/overview) ⌘I --- # Nft - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Nft [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/overview#overview) Overview ------------------------------------------------------------------------------------------- This schema contains 4 tables and views for Flow data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/overview#tables-and-views) Tables and Views ----------------------------------------------------------------------------------------------------------- [Dim Allday Metadata\ -------------------\ \ Comprehensive metadata for NFL All Day Moments, including player information, team details, statistics, and rich content data.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata) [Dim Moment Metadata\ -------------------\ \ NFT moment metadata scraped from on-chain activity across multiple Flow NFT projects.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata) [Dim Ufc Strike Metadata\ -----------------------\ \ Metadata for UFC Strike NFTs, capturing information about UFC-themed digital collectibles on the Flow blockchain.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata) [Ez Nft Sales\ ------------\ \ Comprehensive view of all NFT marketplace sales on the Flow blockchain, providing a unified interface for NFT trading activity across multiple mark…](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales) Was this page helpful? YesNo [Ez Staking Actions](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/ez-staking-actions) [Dim Allday Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata) ⌘I --- # Dim Asset Metadata - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Dim Asset Metadata [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [price\_\_dim\_asset\_metadata](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata#price-dim-asset-metadata) * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata#columns) **Schema**: `flow.price` **Table**: `dim_asset_metadata` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata#price-dim-asset-metadata) price\_\_dim\_asset\_metadata ============================================================================================================================================ [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata#description) Description ------------------------------------------------------------------------------------------------------------- A comprehensive dimensional table containing raw asset metadata from multiple price providers. This table serves as the foundation for asset identification and metadata management across different blockchain networks and price data sources. It contains uncurated, provider-specific data that may include duplicates, inconsistencies, and data quality issues inherent to the source APIs. The table maintains the original provider structure to preserve data lineage and enable source-specific analysis. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata#key-use-cases) Key Use Cases ----------------------------------------------------------------------------------------------------------------- * **Asset Discovery and Identification**: Finding all available assets across different price providers and blockchain networks * **Data Quality Analysis**: Identifying inconsistencies, duplicates, and gaps in asset metadata across providers * **Provider Comparison**: Analyzing how different price providers categorize and describe the same assets * **Cross-Chain Asset Mapping**: Understanding how assets are represented across different blockchain networks * **Data Lineage Tracking**: Maintaining audit trails for asset metadata changes and provider updates * **Raw Data Access**: Providing access to unprocessed asset metadata for custom curation and analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------- * **price\_\_ez\_asset\_metadata**: Curated, deduplicated version of this table with one record per unique asset * **price\_\_fact\_prices\_ohlc\_hourly**: Links to price data through asset\_id and provider * **price\_\_ez\_prices\_hourly**: Provides curated price data for assets in this dimension * **core\_\_dim\_contract\_labels**: May overlap with contract-based assets for additional labeling * **evm/core\_evm\_\_dim\_contracts**: For EVM-based tokens, provides additional contract metadata [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------- * **PROVIDER**: Essential for filtering by data source and understanding data provenance * **ASSET\_ID**: Primary identifier for joining with price fact tables and other asset-related data * **TOKEN\_ADDRESS**: Critical for blockchain-specific operations and smart contract interactions * **BLOCKCHAIN**: Key for cross-chain analysis and blockchain-specific filtering * **SYMBOL**: Commonly used for asset identification in reports and dashboards * **NAME**: Human-readable asset name for display and reporting purposes [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata#columns) Columns ----------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | TOKEN\_ADDRESS | TEXT | The blockchain-specific contract address or identifier for the token asset. Data type: STRING. This field contains the unique address where the token contract is deployed on its respective blockchain network. Used for token identification, contract verification, cross-chain asset mapping, and blockchain-specific operations. Example: ‘0xa0b86a33e6441b8c4c8c8c8c8c8c8c8c8c8c8c8c’ for USDC on Ethereum, NULL for native assets like Bitcoin or Flow. Critical for DeFi operations, smart contract interactions, and maintaining accurate token mappings across different blockchain networks. | | ASSET\_ID | TEXT | The unique identifier representing the asset within the price provider’s system. Data type: STRING. This field serves as the primary key for identifying specific assets across different price providers and data sources. Used for joining price data with asset metadata, tracking price movements over time, and maintaining referential integrity between fact and dimension tables. Example: ‘bitcoin’ for Bitcoin on CoinGecko, ‘ethereum’ for Ethereum on CoinMarketCap. Critical for data lineage, asset identification, and cross-provider data reconciliation in financial analytics and reporting workflows. | | SYMBOL | TEXT | The ticker symbol or abbreviated code representing the asset. Data type: STRING. This field contains the short, standardized identifier used in trading, price displays, and market data. Used for quick asset identification, trading interfaces, price feeds, and cross-platform asset matching. Example: ‘BTC’ for Bitcoin, ‘ETH’ for Ethereum, ‘FLOW’ for Flow, ‘USDC’ for USD Coin. Critical for market data integration, trading operations, and maintaining consistency across different exchanges and price providers. | | NAME | TEXT | The full name of the asset as provided by the price data source. Data type: STRING. This field contains the human-readable, official name of the cryptocurrency, token, or digital asset. Used for display purposes, user interfaces, reporting, and asset identification in analytics dashboards. Example: ‘Bitcoin’ for BTC, ‘Ethereum’ for ETH, ‘Flow’ for FLOW. Important for user experience, data presentation, and maintaining consistency across different price providers and blockchain networks. | | BLOCKCHAIN | TEXT | The blockchain network or platform where the asset is native or primarily traded. Data type: STRING. This field identifies the specific blockchain ecosystem that hosts the asset’s smart contract or where the native asset operates. Used for cross-chain analytics, multi-chain portfolio tracking, and blockchain-specific filtering and grouping. Example: ‘ethereum’ for ETH and ERC-20 tokens, ‘flow’ for FLOW and Flow-native assets, ‘bitcoin’ for BTC. Critical for understanding asset distribution across blockchain networks, cross-chain bridge analysis, and multi-chain DeFi analytics. | | BLOCKCHAIN\_ID | TEXT | The unique numeric identifier for the blockchain network or platform. Data type: INTEGER. This field provides a standardized way to identify blockchain networks across different systems and APIs. Used for blockchain network identification, cross-platform data integration, and maintaining consistent blockchain references. Example: 1 for Ethereum mainnet, 137 for Polygon, 0 for Bitcoin. Important for chain ID validation, cross-chain bridge operations, and maintaining referential integrity in multi-chain analytics systems. | | PROVIDER | TEXT | The data provider or source for the asset metadata or price record. Data type: STRING. This field identifies the external service, API, or protocol that supplied the asset or price data (e.g., ‘CoinGecko’, ‘CoinMarketCap’, ‘Dapper’, ‘Flow Oracle’). Used for data quality analysis, source attribution, and filtering by provider. Example: ‘CoinGecko’ for token prices, ‘Dapper’ for Flow-native asset metadata. Important for understanding data provenance, resolving discrepancies, and ensuring data reliability in analytics workflows. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | | DIM\_ASSET\_METADATA\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | Was this page helpful? YesNo [Price](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/overview) [Ez Asset Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata) ⌘I --- # Ez Asset Metadata - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Ez Asset Metadata [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [price\_\_ez\_asset\_metadata](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata#price-ez-asset-metadata) * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata#columns) **Schema**: `flow.price` **Table**: `ez_asset_metadata` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata#price-ez-asset-metadata) price\_\_ez\_asset\_metadata ========================================================================================================================================= [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata#description) Description ------------------------------------------------------------------------------------------------------------ A curated and deduplicated asset metadata table that provides a single source of truth for asset information across different blockchain networks. This table consolidates data from multiple price providers, resolving conflicts and maintaining one record per unique asset per blockchain. It serves as the primary dimension table for asset identification in price analytics and provides clean, reliable metadata for reporting and analysis. The table prioritizes data quality and consistency over raw data preservation. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata#key-use-cases) Key Use Cases ---------------------------------------------------------------------------------------------------------------- * **Asset Reference**: Primary lookup table for asset metadata in price analytics and reporting * **Portfolio Management**: Providing consistent asset information for multi-asset portfolio tracking * **Price Analysis**: Joining with price fact tables for comprehensive asset price analysis * **Cross-Chain Analytics**: Understanding asset distribution and characteristics across blockchain networks * **Reporting and Dashboards**: Providing clean, consistent asset names and symbols for user interfaces * **Data Quality Assurance**: Ensuring consistent asset representation across different data sources [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------ * **price\_\_dim\_asset\_metadata**: Raw source data that feeds into this curated table * **price\_\_fact\_prices\_ohlc\_hourly**: Links to raw price data through asset\_id * **price\_\_ez\_prices\_hourly**: Primary price table that uses this for asset metadata * **core\_\_dim\_contract\_labels**: Provides additional labeling for contract-based assets * **evm/core\_evm\_\_dim\_contracts**: For EVM tokens, provides additional contract-level metadata [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------ * **TOKEN\_ADDRESS**: Primary identifier for blockchain-specific operations and smart contract interactions * **SYMBOL**: Most commonly used field for asset identification in reports and dashboards * **NAME**: Human-readable asset name for display and user interfaces * **BLOCKCHAIN**: Essential for cross-chain analysis and blockchain-specific filtering * **DECIMALS**: Critical for accurate price calculations and token amount conversions * **IS\_NATIVE**: Important for distinguishing native blockchain tokens from smart contract tokens [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | TOKEN\_ADDRESS | TEXT | The blockchain-specific contract address or identifier for the token asset. Data type: STRING. This field contains the unique address where the token contract is deployed on its respective blockchain network. Used for token identification, contract verification, cross-chain asset mapping, and blockchain-specific operations. Example: ‘0xa0b86a33e6441b8c4c8c8c8c8c8c8c8c8c8c8c8c’ for USDC on Ethereum, NULL for native assets like Bitcoin or Flow. Critical for DeFi operations, smart contract interactions, and maintaining accurate token mappings across different blockchain networks. | | ASSET\_ID | TEXT | The unique identifier representing the asset within the price provider’s system. Data type: STRING. This field serves as the primary key for identifying specific assets across different price providers and data sources. Used for joining price data with asset metadata, tracking price movements over time, and maintaining referential integrity between fact and dimension tables. Example: ‘bitcoin’ for Bitcoin on CoinGecko, ‘ethereum’ for Ethereum on CoinMarketCap. Critical for data lineage, asset identification, and cross-provider data reconciliation in financial analytics and reporting workflows. | | SYMBOL | TEXT | The ticker symbol or abbreviated code representing the asset. Data type: STRING. This field contains the short, standardized identifier used in trading, price displays, and market data. Used for quick asset identification, trading interfaces, price feeds, and cross-platform asset matching. Example: ‘BTC’ for Bitcoin, ‘ETH’ for Ethereum, ‘FLOW’ for Flow, ‘USDC’ for USD Coin. Critical for market data integration, trading operations, and maintaining consistency across different exchanges and price providers. | | NAME | TEXT | The full name of the asset as provided by the price data source. Data type: STRING. This field contains the human-readable, official name of the cryptocurrency, token, or digital asset. Used for display purposes, user interfaces, reporting, and asset identification in analytics dashboards. Example: ‘Bitcoin’ for BTC, ‘Ethereum’ for ETH, ‘Flow’ for FLOW. Important for user experience, data presentation, and maintaining consistency across different price providers and blockchain networks. | | DECIMALS | NUMBER | The number of decimal places used to represent the smallest unit of the asset. Data type: INTEGER. This field indicates the precision with which the asset can be divided and is essential for accurate price calculations and token amount conversions. Used for token amount normalization, price precision calculations, and ensuring accurate financial computations. Example: 18 for most ERC-20 tokens, 8 for Bitcoin, 6 for USDC. Critical for DeFi operations, token transfers, and maintaining precision in financial calculations across different blockchain networks. | | BLOCKCHAIN | TEXT | The blockchain network or platform where the asset is native or primarily traded. Data type: STRING. This field identifies the specific blockchain ecosystem that hosts the asset’s smart contract or where the native asset operates. Used for cross-chain analytics, multi-chain portfolio tracking, and blockchain-specific filtering and grouping. Example: ‘ethereum’ for ETH and ERC-20 tokens, ‘flow’ for FLOW and Flow-native assets, ‘bitcoin’ for BTC. Critical for understanding asset distribution across blockchain networks, cross-chain bridge analysis, and multi-chain DeFi analytics. | | IS\_DEPRECATED | BOOLEAN | A boolean flag indicating whether the asset has been deprecated or is no longer actively supported by the price provider. Data type: BOOLEAN. This field helps identify assets that may have outdated or unreliable price data. Used for data quality filtering, identifying discontinued assets, and ensuring data reliability in analytics and trading operations. Example: TRUE for deprecated tokens or assets no longer listed on exchanges, FALSE for actively traded assets. Critical for data quality management, avoiding stale price data, and maintaining accurate market analytics. | | IS\_NATIVE | BOOLEAN | A boolean flag indicating whether the asset is the native token of its respective blockchain network. Data type: BOOLEAN. This field distinguishes between native blockchain tokens and smart contract-based tokens. Used for filtering native vs. token assets, blockchain-specific analytics, and understanding asset distribution across different token types. Example: TRUE for Bitcoin (BTC), Ethereum (ETH), and Flow (FLOW), FALSE for USDC, DAI, and other smart contract tokens. Important for blockchain economics analysis, native token price tracking, and understanding the relationship between native tokens and their ecosystem tokens. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | | EZ\_ASSET\_METADATA\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | Was this page helpful? YesNo [Dim Asset Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata) [Ez Prices Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly) ⌘I --- # Dim Moment Metadata - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Dim Moment Metadata [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata#columns) **Schema**: `flow.nft` **Table**: `dim_moment_metadata` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata#description) Description ------------------------------------------------------------------------------------------------------------ NFT moment metadata scraped from on-chain activity across multiple Flow NFT projects. This table captures metadata that is stored directly on the blockchain when moments are minted, providing a decentralized source of NFT information. The table supports multiple NFT collections including All Day, TopShot, and Golazos, with comprehensive metadata including play details, series information, and collection hierarchy. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata#key-use-cases) Key Use Cases ---------------------------------------------------------------------------------------------------------------- * Analyze on-chain NFT metadata across multiple collections * Track moment creation and minting activity * Support cross-collection NFT analytics * Enable decentralized metadata verification * Power NFT explorer and discovery tools [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------ * Can be joined with `nft__ez_nft_sales` for sales analytics * Links to `nft__dim_allday_metadata` and `nft__dim_topshot_metadata` for enriched data * NFT collection and ID enable cross-table joins * Supports multiple NFT projects on Flow [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------ * `nft_collection`: Contract address of the NFT collection * `nft_id`: Unique identifier for the NFT moment * `serial_number`: Edition number within the collection * `set_name`: Name of the set containing the moment * `series_name`: Series name for organizational hierarchy * `metadata`: JSON object containing detailed moment information * `tier`: Rarity tier classification [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | NFT\_COLLECTION | TEXT | The contract address or identifier for the NFT collection on the Flow blockchain. Data type: STRING. This field identifies the smart contract that manages the NFT collection, enabling collection-level analytics, filtering, and protocol attribution. Used for grouping NFTs by collection, tracking collection performance, and joining with metadata tables. Example: ‘A.e4cf4bdc1751c65d.AllDay’ for NFL All Day, ‘A.87ca73a41bb50ad5.TopShot’ for NBA TopShot. Important for collection analytics, marketplace filtering, and cross-collection comparisons. | | NFT\_ID | TEXT | The unique identifier for the NFT within its collection. Data type: STRING or NUMBER. This field uniquely identifies a specific NFT token within a collection, typically representing the token ID or serial number assigned during minting. Used for NFT-level analytics, tracking individual token movements, and joining with metadata tables. Example: ‘12345’ for TopShot moment #12345, or ‘A.1234567890abcdef.Moment#456’ for a specific moment. Important for NFT tracking, sales analysis, and metadata joins. | | SERIAL\_NUMBER | TEXT | The serial number or edition number of the NFT within its collection. Data type: NUMBER. This field represents the specific edition number of the NFT, indicating its position within the total circulation of that particular moment or token. Used for rarity analysis, edition tracking, and determining the uniqueness of NFTs within a collection. Example: 25 for the 25th edition of a moment, 1 for the first edition. Important for rarity calculations, edition-based analytics, and determining NFT scarcity within collections. | | MAX\_MINT\_SIZE | TEXT | The gross NFTs minted for the batch. | | PLAY\_ID | TEXT | The numeric ID of the play for the moment. For example, with topshot moment ABC may be a version of Play 123. The play id is 123 and moment metadata is associated with the play, rather than the moment. | | SERIES\_ID | TEXT | The numeric ID for the series of moments or plays. This corresponds with the series column found in some metadata tables. | | SERIES\_NAME | TEXT | The series for this particular set of drops. | | SET\_ID | TEXT | The numeric ID for the set. This corresponds with the set name found in some metadata columns. | | SET\_NAME | TEXT | The name of the NFT set or series in which the moment was released. Data type: STRING. This field identifies the specific set or collection within a broader NFT project, enabling set-level analytics, rarity analysis, and set performance tracking. Used for set attribution, set-based market analysis, and understanding the organizational structure of NFT collections. Example: ‘Base Set’ for TopShot, ‘Genesis’ for All Day. Important for set-based analytics, rarity calculations, and understanding the hierarchical structure of NFT collections. | | EDITION\_ID | TEXT | The numeric ID for the edition of moments. This is likely a bundle of moment NFTs within the same type of play, differentiated by some trait like rarity. | | TIER | TEXT | The tiered rarity of the edition. | | METADATA | OBJECT | A JSON object containing comprehensive metadata for the NFT moment or play. Data type: OBJECT/VARIANT. This field stores detailed information about the NFT including play details, statistics, video URLs, and other descriptive data. Used for rich NFT analysis, content discovery, and detailed moment information retrieval. Example: Contains play statistics, video links, game context, and other moment-specific details. Important for comprehensive NFT analysis, content discovery, and providing rich context for NFT transactions and analytics. | | DIM\_MOMENT\_METADATA\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Dim Allday Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata) [Dim Ufc Strike Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata) ⌘I --- # Dim Ufc Strike Metadata - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Dim Ufc Strike Metadata [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata#columns) **Schema**: `flow.nft` **Table**: `dim_ufc_strike_metadata` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata#description) Description ---------------------------------------------------------------------------------------------------------------- Metadata for UFC Strike NFTs, capturing information about UFC-themed digital collectibles on the Flow blockchain. This table provides comprehensive metadata for UFC Strike moments, including set information, listing details, and rich content data. The table supports UFC Strike marketplace integration and enables analysis of UFC-themed NFT performance and market activity. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata#key-use-cases) Key Use Cases -------------------------------------------------------------------------------------------------------------------- * Analyze UFC Strike NFT performance and market activity * Track UFC-themed digital collectible analytics * Power UFC Strike dashboards and user-facing applications * Support content discovery and moment exploration * Enable UFC event correlation with NFT values [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata#important-relationships) Important Relationships ---------------------------------------------------------------------------------------------------------------------------------------- * Can be joined with `nft__ez_nft_sales` for sales analytics * Links to other NFT metadata tables for cross-collection analysis * UFC Strike ID enables direct marketplace integration * Supports UFC-themed NFT ecosystem analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata#commonly-used-fields) Commonly-used Fields ---------------------------------------------------------------------------------------------------------------------------------- * `nft_id`: Unique identifier for the UFC Strike moment * `serial_number`: Edition number within the collection * `listing_id`: Marketplace listing identifier * `set_name`: Name of the UFC Strike set * `set_description`: Detailed description of the set * `metadata`: JSON object containing detailed moment information [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata#columns) Columns -------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | NFT\_ID | NUMBER | The unique identifier for the NFT within its collection. Data type: STRING or NUMBER. This field uniquely identifies a specific NFT token within a collection, typically representing the token ID or serial number assigned during minting. Used for NFT-level analytics, tracking individual token movements, and joining with metadata tables. Example: ‘12345’ for TopShot moment #12345, or ‘A.1234567890abcdef.Moment#456’ for a specific moment. Important for NFT tracking, sales analysis, and metadata joins. | | SERIAL\_NUMBER | NUMBER | The serial number or edition number of the NFT within its collection. Data type: NUMBER. This field represents the specific edition number of the NFT, indicating its position within the total circulation of that particular moment or token. Used for rarity analysis, edition tracking, and determining the uniqueness of NFTs within a collection. Example: 25 for the 25th edition of a moment, 1 for the first edition. Important for rarity calculations, edition-based analytics, and determining NFT scarcity within collections. | | LISTING\_ID | NUMBER | The listing ID used by the NFT marketplace. | | SET\_NAME | TEXT | The name of the NFT set or series in which the moment was released. Data type: STRING. This field identifies the specific set or collection within a broader NFT project, enabling set-level analytics, rarity analysis, and set performance tracking. Used for set attribution, set-based market analysis, and understanding the organizational structure of NFT collections. Example: ‘Base Set’ for TopShot, ‘Genesis’ for All Day. Important for set-based analytics, rarity calculations, and understanding the hierarchical structure of NFT collections. | | SET\_DESCRIPTION | TEXT | | | METADATA | OBJECT | A JSON object containing comprehensive metadata for the NFT moment or play. Data type: OBJECT/VARIANT. This field stores detailed information about the NFT including play details, statistics, video URLs, and other descriptive data. Used for rich NFT analysis, content discovery, and detailed moment information retrieval. Example: Contains play statistics, video links, game context, and other moment-specific details. Important for comprehensive NFT analysis, content discovery, and providing rich context for NFT transactions and analytics. | | DIM\_UFC\_STRIKE\_METADATA\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Dim Moment Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata) [Ez Nft Sales](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales) ⌘I --- # Dim Allday Metadata - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Dim Allday Metadata [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata#columns) **Schema**: `flow.nft` **Table**: `dim_allday_metadata` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata#description) Description ------------------------------------------------------------------------------------------------------------ Comprehensive metadata for NFL All Day Moments, including player information, team details, statistics, and rich content data. This table is produced via API integration and provides detailed information about each NFL All Day NFT moment, including play descriptions, video URLs, and comprehensive statistics. The data structure may differ from on-chain metadata available in other tables, providing a more complete and curated view of NFL All Day moments. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata#key-use-cases) Key Use Cases ---------------------------------------------------------------------------------------------------------------- * Analyze NFL All Day moment performance and market activity * Track player and team-based NFT analytics * Power NFL All Day dashboards and user-facing applications * Support content discovery and moment exploration * Enable player and team-based market analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------ * Can be joined with `nft__ez_nft_sales` for sales analytics * Links to `nft__dim_moment_metadata` for on-chain data comparison * Player and team data enables cross-platform athlete analysis * NFL All Day ID enables direct marketplace integration [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------ * `nft_id`: Unique identifier for the NFL All Day moment * `nflallday_id`: Official NFL All Day identifier for marketplace integration * `player`: Athlete featured in the moment * `team`: Team affiliation at time of moment * `season`: NFL season when moment occurred * `set_name`: Collection set name for organization * `total_circulation`: Maximum supply for rarity analysis * `moment_description`: Detailed play description [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-allday-metadata#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | NFT\_ID | TEXT | The unique identifier for the NFT within its collection. Data type: STRING or NUMBER. This field uniquely identifies a specific NFT token within a collection, typically representing the token ID or serial number assigned during minting. Used for NFT-level analytics, tracking individual token movements, and joining with metadata tables. Example: ‘12345’ for TopShot moment #12345, or ‘A.1234567890abcdef.Moment#456’ for a specific moment. Important for NFT tracking, sales analysis, and metadata joins. | | NFT\_COLLECTION | TEXT | The contract address or identifier for the NFT collection on the Flow blockchain. Data type: STRING. This field identifies the smart contract that manages the NFT collection, enabling collection-level analytics, filtering, and protocol attribution. Used for grouping NFTs by collection, tracking collection performance, and joining with metadata tables. Example: ‘A.e4cf4bdc1751c65d.AllDay’ for NFL All Day, ‘A.87ca73a41bb50ad5.TopShot’ for NBA TopShot. Important for collection analytics, marketplace filtering, and cross-collection comparisons. | | NFLALLDAY\_ID | TEXT | The unique identifier used by NFL AllDay for the moment. Data type: STRING. This field provides the official NFL AllDay identifier for the moment, enabling direct linking to the marketplace and cross-referencing with external NFL AllDay data. Used for marketplace integration, external data joins, and direct user navigation to moments. Example: Can be used in URL [https://nflallday.com/moments/{nflallday\_id}](https://nflallday.com/moments/%7Bnflallday_id%7D)
to view the moment on the marketplace. Important for marketplace integration, external data correlation, and user experience features. | | SERIAL\_NUMBER | NUMBER | The serial number or edition number of the NFT within its collection. Data type: NUMBER. This field represents the specific edition number of the NFT, indicating its position within the total circulation of that particular moment or token. Used for rarity analysis, edition tracking, and determining the uniqueness of NFTs within a collection. Example: 25 for the 25th edition of a moment, 1 for the first edition. Important for rarity calculations, edition-based analytics, and determining NFT scarcity within collections. | | MOMENT\_TIER | TEXT | | | TOTAL\_CIRCULATION | NUMBER | The total number of NFTs minted for the particular play or moment. Data type: NUMBER. This field represents the maximum supply of NFTs for a specific moment, enabling rarity calculations, scarcity analysis, and market supply understanding. Used for rarity analysis, supply-side market analysis, and determining the relative scarcity of NFTs within a collection. Example: 1000 for a common moment, 10 for a rare moment. Important for rarity calculations, market supply analysis, and understanding NFT scarcity and value drivers. | | MOMENT\_DESCRIPTION | TEXT | A detailed, long-form description of the play or moment captured in the NFT. Data type: STRING. This field provides a comprehensive narrative description of the sports play, including context, key details, and notable aspects of the moment. Used for content discovery, play identification, and providing rich context for NFT analysis. Example: ‘LeBron James hits a game-winning three-pointer with 2.1 seconds remaining in the fourth quarter.’ Important for content discovery, play identification, and providing rich context for NFT transactions and analytics. | | PLAYER | TEXT | The name of the athlete or player featured in the NFT moment. Data type: STRING. This field identifies the sports figure who is the primary subject of the NFT, enabling player-level analytics, performance tracking, and fan engagement analysis. Used for player attribution, performance correlation with NFT values, and fan behavior analysis. Example: ‘LeBron James’ for NBA TopShot, ‘Tom Brady’ for NFL All Day. Important for player-based analytics, fan engagement tracking, and athlete performance correlation with NFT market activity. | | TEAM | TEXT | The sports team that the player represented at the time the NFT moment was captured. Data type: STRING. This field identifies the team affiliation of the featured player, enabling team-level analytics, regional market analysis, and team performance correlation with NFT values. Used for team attribution, regional market analysis, and team-based fan engagement tracking. Example: ‘Los Angeles Lakers’ for NBA TopShot, ‘Tampa Bay Buccaneers’ for NFL All Day. Important for team-based analytics, regional market insights, and team performance correlation with NFT market activity. | | SEASON | TEXT | The sports season during which the NFT moment occurred. Data type: STRING. This field identifies the specific season when the moment was captured, enabling temporal analysis, season-based performance tracking, and historical trend analysis. Used for season-level analytics, performance correlation across seasons, and historical NFT value analysis. Example: ‘2021-22’ for NBA season, ‘2022’ for NFL season. Important for temporal analysis, season-based performance tracking, and understanding how NFT values correlate with seasonal sports performance. | | WEEK | TEXT | The week of the NFL season during which the game occurred. | | CLASSIFICATION | TEXT | The broad category of play that is shown in the moment. | | PLAY\_TYPE | TEXT | The more granular (than play\_category) type of play that is shown in the moment. | | MOMENT\_DATE | TIMESTAMP\_NTZ | When the moment occurred. | | SERIES | TEXT | The series for this particular set of drops. | | SET\_NAME | TEXT | The name of the NFT set or series in which the moment was released. Data type: STRING. This field identifies the specific set or collection within a broader NFT project, enabling set-level analytics, rarity analysis, and set performance tracking. Used for set attribution, set-based market analysis, and understanding the organizational structure of NFT collections. Example: ‘Base Set’ for TopShot, ‘Genesis’ for All Day. Important for set-based analytics, rarity calculations, and understanding the hierarchical structure of NFT collections. | | VIDEO\_URLS | ARRAY | An array containing links to the moments. | | MOMENT\_STATS\_FULL | OBJECT | A dictionary of the full moment stats. | | DIM\_ALLDAY\_METADATA\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Nft](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/overview) [Dim Moment Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-moment-metadata) ⌘I --- # Ez Nft Sales - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Ez Nft Sales [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales#columns) **Schema**: `flow.nft` **Table**: `ez_nft_sales` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales#description) Description ----------------------------------------------------------------------------------------------------- Comprehensive view of all NFT marketplace sales on the Flow blockchain, providing a unified interface for NFT trading activity across multiple marketplaces and collections. This table captures sales from the primary NFT Marketplace contract, Fabricant NFT Marketplace, NBA TopShot primary market, and other supported marketplaces. The table includes transaction details, pricing information, and marketplace attribution, enabling cross-platform NFT sales analysis. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales#key-use-cases) Key Use Cases --------------------------------------------------------------------------------------------------------- * Analyze NFT sales activity across multiple marketplaces * Track collection and marketplace performance * Power NFT market dashboards and analytics * Support price analysis and market trends * Enable cross-collection and cross-marketplace comparisons [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales#important-relationships) Important Relationships ----------------------------------------------------------------------------------------------------------------------------- * Sources data from `silver__nft_sales_s` for unified sales data * Can be joined with metadata tables (`nft__dim_allday_metadata`, `nft__dim_topshot_metadata`, etc.) for enriched analytics * Links to `nft__fact_topshot_buybacks` for buyback program analysis * Supports multiple NFT collections and marketplaces [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales#commonly-used-fields) Commonly-used Fields ----------------------------------------------------------------------------------------------------------------------- * `tx_id`: Unique transaction identifier for the sale * `block_timestamp`: When the sale transaction occurred * `marketplace`: Name of the marketplace where sale occurred * `nft_collection`: Contract address of the NFT collection * `nft_id`: Unique identifier for the NFT sold * `buyer`: Address of the buyer * `seller`: Address of the seller * `price`: Sale price in the specified currency * `currency`: Currency used for the transaction [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales#columns) Columns --------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | TX\_ID | TEXT | The unique identifier (hash) for a transaction on the Flow blockchain. Data type: STRING. Each transaction is assigned a cryptographic hash that ensures its uniqueness and immutability. Used for joining transaction data across tables, tracing transaction execution, and verifying transaction integrity. Example: ‘e3f1c2d4…’. Essential for transaction-level analytics, debugging, and cross-referencing with block and event data. | | BLOCK\_HEIGHT | NUMBER | Block height is the unique, sequential integer assigned to each block as it is added to the Flow blockchain. It serves as the primary identifier for block ordering and is used to reference the position of a block within the chain. Data type: INTEGER. Block height is essential for joining block, transaction, and event tables, and for analyzing blockchain growth over time. For example, block height 100,000 refers to the 100,000th block produced on Flow. This field is critical for time-series analytics, chain reorganization analysis, and historical state reconstruction. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The timestamp (in UTC) when the block or transaction was recorded on the Flow blockchain. Data type: TIMESTAMP\_NTZ. This field is essential for time-series analysis, ordering events, and joining with other tables by time. For example, a block with block\_height 100,000 may have a block\_timestamp of ‘2023-01-01 12:00:00’. Used for analytics on network activity, transaction throughput, and historical state reconstruction. | | MARKETPLACE | TEXT | Contract address for the marketplace where the transaction occurred. Flow uses a general-purpose contract at `A.4eb8a10cb9f87357.NFTStorefront` for a significant number of sales. This column does not necessarily indicate the website or specific platform on which the sale occurred. | | NFT\_COLLECTION | TEXT | The contract address or identifier for the NFT collection on the Flow blockchain. Data type: STRING. This field identifies the smart contract that manages the NFT collection, enabling collection-level analytics, filtering, and protocol attribution. Used for grouping NFTs by collection, tracking collection performance, and joining with metadata tables. Example: ‘A.e4cf4bdc1751c65d.AllDay’ for NFL All Day, ‘A.87ca73a41bb50ad5.TopShot’ for NBA TopShot. Important for collection analytics, marketplace filtering, and cross-collection comparisons. | | NFT\_ID | TEXT | The unique identifier for the NFT within its collection. Data type: STRING or NUMBER. This field uniquely identifies a specific NFT token within a collection, typically representing the token ID or serial number assigned during minting. Used for NFT-level analytics, tracking individual token movements, and joining with metadata tables. Example: ‘12345’ for TopShot moment #12345, or ‘A.1234567890abcdef.Moment#456’ for a specific moment. Important for NFT tracking, sales analysis, and metadata joins. | | BUYER | TEXT | The party in the transaction purchasing the asset, this is an account address. | | SELLER | TEXT | The party in the transaction selling the asset, this is an account address. | | PRICE | FLOAT | The price of the asset, in the currency specified in the table. | | CURRENCY | TEXT | The contract address refering to the currency used in the transaction. This may or may not relate to a token in the prices table, depending on the marketplace or transaction. | | TX\_SUCCEEDED | BOOLEAN | Transaction status, if it succeeded or failed. | | TOKENFLOW | ARRAY | An array of events tracking the flow of tokens, in event\_index order, for a transaction. This is constructed from the following events within a transaction: `TokensDeposited`, `TokensWithdrawn`, `ForwardedDeposit`. | | COUNTERPARTIES | ARRAY | An array containing the addresses interacted with during the tokenflow of the transaction. This contains all payers and recipients of tokens within the transaction. | | EZ\_NFT\_SALES\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | Was this page helpful? YesNo [Dim Ufc Strike Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/dim-ufc-strike-metadata) [Price](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/overview) ⌘I --- # Fact Prices Ohlc Hourly - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Fact Prices Ohlc Hourly [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [price\_\_fact\_prices\_ohlc\_hourly](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly#price-fact-prices-ohlc-hourly) * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly#columns) **Schema**: `flow.price` **Table**: `fact_prices_ohlc_hourly` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly#price-fact-prices-ohlc-hourly) price\_\_fact\_prices\_ohlc\_hourly ============================================================================================================================================================ [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly#description) Description ------------------------------------------------------------------------------------------------------------------ A comprehensive fact table containing raw OHLC (Open, High, Low, Close) price data at hourly intervals from multiple price providers. This table preserves the original provider structure and contains uncurated price data that may include duplicates, inconsistencies, and data quality issues inherent to the source APIs. It serves as the foundation for price analysis while maintaining data lineage and enabling provider-specific analysis. The table supports detailed price movement analysis and technical indicator calculations. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly#key-use-cases) Key Use Cases ---------------------------------------------------------------------------------------------------------------------- * **Technical Analysis**: Calculating technical indicators, support/resistance levels, and price patterns * **Volatility Analysis**: Measuring price volatility and risk metrics across different time periods * **Provider Comparison**: Analyzing price differences and data quality across different price providers * **Data Quality Assessment**: Identifying gaps, anomalies, and inconsistencies in price data * **Raw Data Access**: Providing access to unprocessed price data for custom analysis and backtesting * **Historical Price Analysis**: Conducting detailed historical price movement analysis and research [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------------ * **price\_\_dim\_asset\_metadata**: Links to asset metadata through asset\_id and provider * **price\_\_ez\_asset\_metadata**: Provides curated asset information for analysis * **price\_\_ez\_prices\_hourly**: Curated, deduplicated version of this table with one price per asset per hour * **core\_\_fact\_blocks**: May be used for blockchain-specific price analysis and correlation studies * **core\_\_fact\_transactions**: For transaction value analysis and price impact studies [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------------ * **HOUR**: Essential for time-series analysis and temporal data aggregation * **ASSET\_ID**: Primary identifier for joining with asset metadata and other price-related data * **OPEN**: Starting price for the hour, used in OHLC analysis and trend calculations * **HIGH**: Maximum price during the hour, important for resistance level analysis * **LOW**: Minimum price during the hour, important for support level analysis * **CLOSE**: Ending price for the hour, most commonly used for price trend analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly#columns) Columns ---------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | ASSET\_ID | TEXT | The unique identifier representing the asset within the price provider’s system. Data type: STRING. This field serves as the primary key for identifying specific assets across different price providers and data sources. Used for joining price data with asset metadata, tracking price movements over time, and maintaining referential integrity between fact and dimension tables. Example: ‘bitcoin’ for Bitcoin on CoinGecko, ‘ethereum’ for Ethereum on CoinMarketCap. Critical for data lineage, asset identification, and cross-provider data reconciliation in financial analytics and reporting workflows. | | HOUR | TIMESTAMP\_NTZ | The timestamp representing the hour when the price data was recorded or aggregated. Data type: TIMESTAMP. This field provides the temporal reference for hourly price data and is used for time-series analysis, price trend calculations, and temporal data aggregation. Used for hourly price tracking, time-based filtering, and chronological analysis of price movements. Example: ‘2024-01-15 14:00:00’ for the hour starting at 2 PM on January 15, 2024. Critical for time-series analytics, price volatility calculations, and maintaining temporal consistency in financial data analysis. | | OPEN | FLOAT | The opening price of the asset at the beginning of the specified hour, denominated in USD. Data type: FLOAT. This field represents the first trading price of the asset during the hour and is used for OHLC (Open, High, Low, Close) price analysis and volatility calculations. Used for price range analysis, volatility measurement, and technical analysis indicators. Example: 44000.00 for Bitcoin opening at $44,000.00 USD per BTC at the start of the hour. Critical for candlestick chart analysis, price momentum calculations, and understanding intra-hour price movements. | | HIGH | FLOAT | The highest trading price of the asset during the specified hour, denominated in USD. Data type: FLOAT. This field represents the peak price reached by the asset within the hour and is used for price range analysis and volatility calculations. Used for resistance level analysis, volatility measurement, and understanding price extremes during trading periods. Example: 46000.00 for Bitcoin reaching a high of $46,000.00 USD per BTC during the hour. Critical for technical analysis, price range calculations, and understanding market sentiment and price momentum. | | LOW | FLOAT | The lowest trading price of the asset during the specified hour, denominated in USD. Data type: FLOAT. This field represents the minimum price reached by the asset within the hour and is used for price range analysis and volatility calculations. Used for support level analysis, volatility measurement, and understanding price extremes during trading periods. Example: 43000.00 for Bitcoin reaching a low of $43,000.00 USD per BTC during the hour. Critical for technical analysis, price range calculations, and understanding market sentiment and price momentum. | | CLOSE | FLOAT | The closing price of the asset at the end of the specified hour, denominated in USD. Data type: FLOAT. This field represents the final trading price of the asset during the hour and is used for OHLC (Open, High, Low, Close) price analysis and trend calculations. Used for price trend analysis, momentum calculations, and technical indicator computations. Example: 45000.50 for Bitcoin closing at $45,000.50 USD per BTC at the end of the hour. Critical for candlestick chart analysis, price trend identification, and understanding market direction and momentum. | | PROVIDER | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | | FACT\_PRICES\_OHLC\_HOURLY\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | Was this page helpful? YesNo [Ez Prices Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly) [Rewards](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/overview) ⌘I --- # Flow Data - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Flow Flow Data [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/flow/overview#overview) * [Available Schemas](https://docs.flipsidecrypto.xyz/blockchain-data/flow/overview#available-schemas) [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/overview#overview) Overview --------------------------------------------------------------------------------------- This section contains comprehensive documentation for all Flow data available through Flipside Crypto.[View DBT Documentation\ ----------------------\ \ View the complete technical documentation and data lineage for Flow models](https://flipsidecrypto.github.io/flow-models/) [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/overview#available-schemas) Available Schemas --------------------------------------------------------------------------------------------------------- [Beta\ ----\ \ Tables and views in the flow.beta schema](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/overview) [Core Evm\ --------\ \ Tables and views in the flow.core\_evm schema](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core-evm/overview) [Core Tables\ -----------\ \ Tables and views in the flow.core schema](https://docs.flipsidecrypto.xyz/blockchain-data/flow/core/overview) [Defi\ ----\ \ Tables and views in the flow.defi schema](https://docs.flipsidecrypto.xyz/blockchain-data/flow/defi/overview) [Gov\ ---\ \ Tables and views in the flow.gov schema](https://docs.flipsidecrypto.xyz/blockchain-data/flow/gov/overview) [Nft\ ---\ \ Tables and views in the flow.nft schema](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/overview) [Price\ -----\ \ Tables and views in the flow.price schema](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/overview) [Rewards\ -------\ \ Tables and views in the flow.rewards schema](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/overview) [Stats\ -----\ \ Tables and views in the flow.stats schema](https://docs.flipsidecrypto.xyz/blockchain-data/flow/stats/overview) [Testnet\ -------\ \ Tables and views in the flow.testnet schema](https://docs.flipsidecrypto.xyz/blockchain-data/flow/testnet/overview) Was this page helpful? YesNo [Fact Prices Ohlc Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/ethereum/price/fact-prices-ohlc-hourly) [Beta](https://docs.flipsidecrypto.xyz/blockchain-data/flow/beta/overview) ⌘I --- # Stats - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/stats/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Stats Stats [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/flow/stats/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/flow/stats/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/stats/overview#overview) Overview --------------------------------------------------------------------------------------------- This schema contains 1 tables and views for Flow data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/stats/overview#tables-and-views) Tables and Views ------------------------------------------------------------------------------------------------------------- [Ez Core Metrics Hourly\ ----------------------\ \ A comprehensive metrics table that aggregates core blockchain performance indicators on an hourly basis.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/stats/ez-core-metrics-hourly) Was this page helpful? YesNo [Fact Points Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-transfers) [Ez Core Metrics Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/flow/stats/ez-core-metrics-hourly) ⌘I --- # Ez Prices Hourly - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Ez Prices Hourly [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [price\_\_ez\_prices\_hourly](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly#price-ez-prices-hourly) * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly#columns) **Schema**: `flow.price` **Table**: `ez_prices_hourly` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly#price-ez-prices-hourly) price\_\_ez\_prices\_hourly ====================================================================================================================================== [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly#description) Description ----------------------------------------------------------------------------------------------------------- A curated and deduplicated hourly price table that provides a single source of truth for asset prices across different blockchain networks. This table consolidates price data from multiple providers, resolving conflicts and maintaining one price per unique asset per hour. It serves as the primary price table for analytics, reporting, and portfolio management, providing clean, reliable price data that prioritizes data quality and consistency. The table includes comprehensive asset metadata for easy analysis and reporting. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly#key-use-cases) Key Use Cases --------------------------------------------------------------------------------------------------------------- * **Portfolio Valuation**: Calculating current and historical portfolio values across multiple assets * **Price Analysis**: Conducting price trend analysis and market performance evaluation * **Cross-Chain Analytics**: Comparing asset performance across different blockchain networks * **Reporting and Dashboards**: Providing clean price data for user interfaces and automated reporting * **Risk Management**: Monitoring price movements and calculating risk metrics * **Trading Operations**: Supporting trading decisions with reliable price data [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly#important-relationships) Important Relationships ----------------------------------------------------------------------------------------------------------------------------------- * **price\_\_fact\_prices\_ohlc\_hourly**: Raw source data that feeds into this curated table * **price\_\_ez\_asset\_metadata**: Provides comprehensive asset metadata for analysis * **price\_\_dim\_asset\_metadata**: Raw asset metadata source for additional provider-specific information * **core\_\_fact\_transactions**: For transaction value analysis and price impact correlation studies * **defi\_\_fact\_dex\_swaps**: For DeFi trading analysis and price impact on swap volumes [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly#commonly-used-fields) Commonly-used Fields ----------------------------------------------------------------------------------------------------------------------------- * **HOUR**: Essential for time-series analysis and temporal data aggregation * **TOKEN\_ADDRESS**: Primary identifier for blockchain-specific operations and smart contract interactions * **SYMBOL**: Most commonly used field for asset identification in reports and dashboards * **PRICE**: Core price field used for valuation, analysis, and reporting * **BLOCKCHAIN**: Essential for cross-chain analysis and blockchain-specific filtering * **IS\_IMPUTED**: Important for data quality assessment and filtering potentially unreliable prices [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly#columns) Columns --------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | HOUR | TIMESTAMP\_NTZ | The timestamp representing the hour when the price data was recorded or aggregated. Data type: TIMESTAMP. This field provides the temporal reference for hourly price data and is used for time-series analysis, price trend calculations, and temporal data aggregation. Used for hourly price tracking, time-based filtering, and chronological analysis of price movements. Example: ‘2024-01-15 14:00:00’ for the hour starting at 2 PM on January 15, 2024. Critical for time-series analytics, price volatility calculations, and maintaining temporal consistency in financial data analysis. | | TOKEN\_ADDRESS | TEXT | The blockchain-specific contract address or identifier for the token asset. Data type: STRING. This field contains the unique address where the token contract is deployed on its respective blockchain network. Used for token identification, contract verification, cross-chain asset mapping, and blockchain-specific operations. Example: ‘0xa0b86a33e6441b8c4c8c8c8c8c8c8c8c8c8c8c8c’ for USDC on Ethereum, NULL for native assets like Bitcoin or Flow. Critical for DeFi operations, smart contract interactions, and maintaining accurate token mappings across different blockchain networks. | | SYMBOL | TEXT | The ticker symbol or abbreviated code representing the asset. Data type: STRING. This field contains the short, standardized identifier used in trading, price displays, and market data. Used for quick asset identification, trading interfaces, price feeds, and cross-platform asset matching. Example: ‘BTC’ for Bitcoin, ‘ETH’ for Ethereum, ‘FLOW’ for Flow, ‘USDC’ for USD Coin. Critical for market data integration, trading operations, and maintaining consistency across different exchanges and price providers. | | NAME | TEXT | | | DECIMALS | NUMBER | The number of decimal places used to represent the smallest unit of the asset. Data type: INTEGER. This field indicates the precision with which the asset can be divided and is essential for accurate price calculations and token amount conversions. Used for token amount normalization, price precision calculations, and ensuring accurate financial computations. Example: 18 for most ERC-20 tokens, 8 for Bitcoin, 6 for USDC. Critical for DeFi operations, token transfers, and maintaining precision in financial calculations across different blockchain networks. | | PRICE | FLOAT | The closing price of the asset for the specified hour, denominated in USD. Data type: FLOAT. This field represents the final trading price of the asset during the hour and is used for price analysis, portfolio valuation, and market performance calculations. Used for price trend analysis, asset valuation, and financial reporting. Example: 45000.50 for Bitcoin price at $45,000.50 USD per BTC. Critical for portfolio management, price impact analysis, and maintaining accurate financial records for trading and investment operations. | | BLOCKCHAIN | TEXT | The blockchain network or platform where the asset is native or primarily traded. Data type: STRING. This field identifies the specific blockchain ecosystem that hosts the asset’s smart contract or where the native asset operates. Used for cross-chain analytics, multi-chain portfolio tracking, and blockchain-specific filtering and grouping. Example: ‘ethereum’ for ETH and ERC-20 tokens, ‘flow’ for FLOW and Flow-native assets, ‘bitcoin’ for BTC. Critical for understanding asset distribution across blockchain networks, cross-chain bridge analysis, and multi-chain DeFi analytics. | | IS\_NATIVE | BOOLEAN | A boolean flag indicating whether the asset is the native token of its respective blockchain network. Data type: BOOLEAN. This field distinguishes between native blockchain tokens and smart contract-based tokens. Used for filtering native vs. token assets, blockchain-specific analytics, and understanding asset distribution across different token types. Example: TRUE for Bitcoin (BTC), Ethereum (ETH), and Flow (FLOW), FALSE for USDC, DAI, and other smart contract tokens. Important for blockchain economics analysis, native token price tracking, and understanding the relationship between native tokens and their ecosystem tokens. | | IS\_IMPUTED | BOOLEAN | A boolean flag indicating whether the price data was imputed or derived from previous records rather than being directly observed. Data type: BOOLEAN. This field helps identify price data that may be less reliable due to low liquidity or inconsistent reporting from the source. Used for data quality assessment, filtering out potentially unreliable price data, and understanding data completeness. Example: TRUE for low-liquidity tokens with infrequent trading, FALSE for actively traded assets with regular price updates. Critical for data quality management, risk assessment, and ensuring accurate price analysis for trading and investment decisions. | | IS\_DEPRECATED | BOOLEAN | A boolean flag indicating whether the asset has been deprecated or is no longer actively supported by the price provider. Data type: BOOLEAN. This field helps identify assets that may have outdated or unreliable price data. Used for data quality filtering, identifying discontinued assets, and ensuring data reliability in analytics and trading operations. Example: TRUE for deprecated tokens or assets no longer listed on exchanges, FALSE for actively traded assets. Critical for data quality management, avoiding stale price data, and maintaining accurate market analytics. | | IS\_VERIFIED | BOOLEAN | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP\_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP\_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt. | | EZ\_PRICES\_HOURLY\_ID | TEXT | `pk_id` is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness. | Was this page helpful? YesNo [Ez Asset Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata) [Fact Prices Ohlc Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly) ⌘I --- # Dim Storefront Items - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Rewards Dim Storefront Items [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [rewards\_\_dim\_storefront\_items](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items#rewards-dim-storefront-items) * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items#columns) **Schema**: `flow.rewards` **Table**: `dim_storefront_items` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items#rewards-dim-storefront-items) rewards\_\_dim\_storefront\_items ======================================================================================================================================================== [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items#description) Description ----------------------------------------------------------------------------------------------------------------- A comprehensive dimensional table containing storefront item metadata from the Minting Assets API. This table serves as the foundation for understanding the rewards storefront inventory, including NFTs, physical items, and digital assets available for purchase with reward points. It contains detailed information about item characteristics, pricing, availability, and redemption mechanics. The table supports the rewards ecosystem by providing item metadata for storefront operations and user experience. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items#key-use-cases) Key Use Cases --------------------------------------------------------------------------------------------------------------------- * **Storefront Management**: Understanding available items, pricing, and inventory levels in the rewards storefront * **Item Discovery**: Finding items by category, price range, or availability status * **Redemption Analysis**: Tracking item redemption patterns and user preferences * **Inventory Planning**: Monitoring item quantities, minting status, and supply management * **User Experience**: Providing item details, images, and metadata for storefront displays * **Reward Program Optimization**: Analyzing which items drive user engagement and point spending [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items#important-relationships) Important Relationships ----------------------------------------------------------------------------------------------------------------------------------------- * **rewards\_\_fact\_points\_balances**: Links to user point balances for purchase eligibility analysis * **rewards\_\_fact\_points\_transfers**: Tracks point spending on storefront purchases * **rewards\_\_fact\_transaction\_entries**: Provides detailed transaction history for item purchases * **nft\_\_dim\_moment\_metadata**: May overlap with NFT items for additional metadata * **core\_\_dim\_contract\_labels**: For contract-based items, provides additional labeling [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items#commonly-used-fields) Commonly-used Fields ----------------------------------------------------------------------------------------------------------------------------------- * **ITEM\_ID**: Primary identifier for storefront items and purchase tracking * **NAME**: Human-readable item name for display and reporting * **PRICE**: Item cost in reward points or currency for purchase analysis * **QUANTITY**: Available inventory for supply management and availability tracking * **MINT\_STATUS**: Current minting status for understanding item availability * **IS\_LISTED**: Flag indicating whether item is currently available for purchase [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items#columns) Columns --------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | ITEM\_ID | TEXT | | | CREATED\_AT | TIMESTAMP\_NTZ | | | ADDITIONAL\_MEDIA | VARIANT | | | ANIMATION\_URL | TEXT | | | ARTIST\_INFO | VARIANT | | | ASSET\_NR | TEXT | | | ATTRIBUTES | VARIANT | | | AUCTION\_ID | TEXT | | | AUCTION\_ITEMS | VARIANT | | | BURN\_TO\_REDEEM\_DETAILS | VARIANT | | | BURN\_TO\_REDEEM\_TYPE | TEXT | | | BURNED\_AT | TIMESTAMP\_NTZ | | | CONTRACT\_ADDRESS | TEXT | | | CURRENCY\_ADDRESS | TEXT | | | CURRENCY\_DECIMALS | NUMBER | | | DELETED\_AT | TIMESTAMP\_NTZ | | | DESCRIPTION | TEXT | | | DOES\_REQUIRE\_W9 | BOOLEAN | | | ENABLE\_BURN\_TO\_REDEEM | BOOLEAN | | | IMAGE\_URL | TEXT | | | IS\_LISTED | BOOLEAN | | | IS\_PHYGITAL\_ITEM | BOOLEAN | | | IS\_PRICE\_IN\_USD | BOOLEAN | | | IS\_REDEEMABLE\_SEPARATE\_FROM\_PURCHASE | BOOLEAN | | | LISTING\_ENDS\_AT | TIMESTAMP\_NTZ | | | LISTING\_STARTS\_AT | TIMESTAMP\_NTZ | | | LISTING\_TYPE | TEXT | | | LOYALTY\_CURRENCY | TEXT | | | LOYALTY\_CURRENCY\_ID | TEXT | | | METADATA\_URI | TEXT | | | MINT\_STATUS | TEXT | | | MINTING\_CONTRACT | TEXT | | | MINTING\_CONTRACT\_ASSET\_MINT\_STATUS | TEXT | | | MINTING\_CONTRACT\_ID | TEXT | | | NAME | TEXT | | | NETWORK | TEXT | | | ORGANIZATION\_ID | TEXT | | | PER\_USER\_MINT\_LIMIT | NUMBER | | | PER\_USER\_MINT\_MIN\_LIMIT | NUMBER | | | PRE\_REVEAL\_MEDIA | VARIANT | | | PRICE | NUMBER | | | QUANTITY | NUMBER | | | QUANTITY\_MINTED | NUMBER | | | REDEEMABLE\_UNTIL | TIMESTAMP\_NTZ | | | REVEALED\_AT | TIMESTAMP\_NTZ | | | SHIPPING\_PRICE | NUMBER | | | SHIPPING\_WITHIN | TEXT | | | STATUS\_TRACKER | TEXT | | | TOKEN\_ID | TEXT | | | TOKEN\_TYPE | TEXT | | | UPDATED\_AT | TIMESTAMP\_NTZ | | | WEBSITE\_ID | TEXT | | | RESPONSE\_JSON | VARIANT | | | DIM\_STOREFRONT\_ITEMS\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | | REQUEST\_TIMESTAMP | TIMESTAMP\_LTZ | | Was this page helpful? YesNo [Rewards](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/overview) [Fact Points Balances](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances) ⌘I --- # Price - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Price [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/overview#overview) Overview --------------------------------------------------------------------------------------------- This schema contains 4 tables and views for Flow data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/overview#tables-and-views) Tables and Views ------------------------------------------------------------------------------------------------------------- [Dim Asset Metadata\ ------------------\ \ A comprehensive dimensional table containing raw asset metadata from multiple price providers.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata) [Ez Asset Metadata\ -----------------\ \ A curated and deduplicated asset metadata table that provides a single source of truth for asset information across different blockchain networks.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-asset-metadata) [Ez Prices Hourly\ ----------------\ \ A curated and deduplicated hourly price table that provides a single source of truth for asset prices across different blockchain networks.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/ez-prices-hourly) [Fact Prices Ohlc Hourly\ -----------------------\ \ A comprehensive fact table containing raw OHLC (Open, High, Low, Close) price data at hourly intervals from multiple price providers.](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/fact-prices-ohlc-hourly) Was this page helpful? YesNo [Ez Nft Sales](https://docs.flipsidecrypto.xyz/blockchain-data/flow/nft/ez-nft-sales) [Dim Asset Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/flow/price/dim-asset-metadata) ⌘I --- # Fact Points Transfers - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-transfers#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Rewards Fact Points Transfers [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-transfers#columns) **Schema**: `flow.rewards` **Table**: `fact_points_transfers` **Type**: View Unified rewards points transfer table combining legacy Flow Points API and new Snag Loyalty API data. **Data Sources:** * **Legacy** (source=‘legacy’): Oct 2024 - Apr 14, 2025 from Flow Points API * **Snag** (source=‘snag’): Apr 16, 2025 onwards from Snag Loyalty API [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-transfers#columns) Columns ---------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | POINT\_ID | TEXT | Unique identifier for the points transaction (batch\_id for legacy, entry\_id for snag) | | SOURCE | TEXT | Data source indicator: ‘legacy’ for Flow Points API or ‘snag’ for Snag Loyalty API | | CREATED\_AT | TIMESTAMP\_NTZ | The date of the transfer | | BATCH\_INDEX | NUMBER | Index of the batch (legacy) or transaction entry (snag) | | TRANSFER\_INDEX | NUMBER | Legacy only: Index of the individual transfer within a batch. NULL for snag data. | | FROM\_ADDRESS | TEXT | EVM address of the user involved in the transaction | | TO\_ADDRESS | TEXT | Legacy only: EVM address of the recipient. NULL for snag data. | | BOXES | NUMBER | Legacy only: Number of boxes transferred. NULL for snag data. | | KEYS | NUMBER | Legacy only: Number of keys transferred. NULL for snag data. | | POINTS | NUMBER | Number of points involved in the transaction | | DIRECTION | TEXT | Snag only: Transaction direction - ‘credit’ for points earned or ‘debit’ for points spent. NULL for legacy data. | | AMOUNT\_START | NUMBER | Snag only: Loyalty account balance before the transaction. NULL for legacy data. | | AMOUNT\_END | NUMBER | Snag only: Loyalty account balance after the transaction. NULL for legacy data. | | ACCOUNT\_ID | TEXT | Snag only: Loyalty account identifier. NULL for legacy data. | | USER\_ID | TEXT | Snag only: User identifier associated with the loyalty account. NULL for legacy data. | | USER\_WALLET\_ADDRESS | TEXT | EVM wallet address of the user (maps from from\_address for legacy, native field for snag) | | TRANSACTION\_ID | TEXT | Snag only: Parent loyalty transaction identifier. NULL for legacy data. | | DATA | OBJECT | Snag only: Full raw JSON response from the API. NULL for legacy data. | | PARTITION\_KEY | NUMBER | Snag only: Partition key for efficient querying. NULL for legacy data. | | INDEX | NUMBER | Snag only: Index of the transaction entry within the partition. NULL for legacy data. | | \_INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | Snag only: Timestamp when the record was inserted into the warehouse. NULL for legacy data. | | FACT\_POINTS\_TRANSFERS\_ID | TEXT | Surrogate primary key for the table | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | UTC timestamp when the record was first inserted into this table | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | UTC timestamp when this record was last modified | | \_INVOCATION\_ID | TEXT | | Was this page helpful? YesNo [Fact Points Balances](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances) [Stats](https://docs.flipsidecrypto.xyz/blockchain-data/flow/stats/overview) ⌘I --- # Fact Points Balances - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Rewards Fact Points Balances [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [rewards\_\_fact\_points\_balances](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances#rewards-fact-points-balances) * [Description](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances#description) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances#commonly-used-fields) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances#columns) **Schema**: `flow.rewards` **Table**: `fact_points_balances` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances#rewards-fact-points-balances) rewards\_\_fact\_points\_balances ======================================================================================================================================================== [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances#description) Description ----------------------------------------------------------------------------------------------------------------- A fact table containing point-in-time balances for user reward accounts from the Reward Points API. This table provides snapshots of user balances including points, boxes, and keys at specific request dates. The data represents balance states rather than transaction flows, with early data potentially being patchy due to API limitations. The table supports reward program analytics by providing current and historical balance information for user engagement analysis and program performance tracking. [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances#key-use-cases) Key Use Cases --------------------------------------------------------------------------------------------------------------------- * **Balance Tracking**: Monitoring current and historical user reward balances across different asset types * **User Engagement Analysis**: Understanding user participation levels and reward accumulation patterns * **Program Performance**: Analyzing reward program effectiveness and user retention * **Balance Reconciliation**: Verifying account balances and identifying data quality issues * **Reward Distribution Analysis**: Understanding how rewards are distributed across the user base * **Predictive Analytics**: Using balance patterns to predict user behavior and program outcomes [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances#important-relationships) Important Relationships ----------------------------------------------------------------------------------------------------------------------------------------- * **rewards\_\_fact\_points\_transfers**: Provides transaction history that explains balance changes * **rewards\_\_fact\_transaction\_entries**: Offers detailed transaction-level data for balance reconciliation * **rewards\_\_dim\_storefront\_items**: Links to items that can be purchased with accumulated points * **core\_\_dim\_address\_mapping**: May link to user addresses for additional user context * **evm/core\_evm\_\_dim\_contracts**: For contract-based reward systems, provides contract metadata [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances#commonly-used-fields) Commonly-used Fields ----------------------------------------------------------------------------------------------------------------------------------- * **ADDRESS**: Primary identifier for user accounts and balance tracking * **POINTS**: Core reward currency balance for program analysis * **BOXES**: Special reward item balance for gamification analysis * **KEYS**: Special reward item balance for access control analysis * **REQUEST\_DATE**: Temporal reference for balance snapshots and time-series analysis * **BOXES\_OPENED**: Historical metric for user engagement and reward consumption [​](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-balances#columns) Columns --------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | ADDRESS | TEXT | The EVM address of the account | | BOXES | NUMBER | The number of boxes owned by the account at the time of the request | | BOXES\_OPENED | NUMBER | The number of boxes opened by the account at the time of the request | | KEYS | NUMBER | The number of keys owned by the account at the time of the request | | POINTS | NUMBER | The number of points accrued by the account at the time of the request | | REQUEST\_DATE | DATE | The date of the request | | FACT\_POINTS\_BALANCES\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | Was this page helpful? YesNo [Dim Storefront Items](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/dim-storefront-items) [Fact Points Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/flow/rewards/fact-points-transfers) ⌘I --- # Gov - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/gov/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Gov Gov [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/gov/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/gov/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/gov/overview#overview) Overview ----------------------------------------------------------------------------------------------- This schema contains 1 tables and views for Optimism data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/gov/overview#tables-and-views) Tables and Views --------------------------------------------------------------------------------------------------------------- [Fact Delegations\ ----------------\ \ This table contains the details of the OP Delegations made by users on the Optimism network.](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/gov/fact-delegations) Was this page helpful? YesNo [Ez Lending Withdraws](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-lending-withdraws) [Fact Delegations](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/gov/fact-delegations) ⌘I --- # Fact Delegations - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/gov/fact-delegations#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Gov Fact Delegations [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/gov/fact-delegations#columns) **Schema**: `optimism.gov` **Table**: `fact_delegations` **Type**: View This table contains the details of the OP Delegations made by users on the Optimism network. [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/gov/fact-delegations#columns) Columns ----------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | STATUS | TEXT | The status of the tx, can be “Success” or “Failed” | | EVENT\_NAME | TEXT | | | DELEGATOR | TEXT | The address of the delegator | | DELEGATE | TEXT | The address of the delegate | | DELEGATION\_TYPE | TEXT | The type of delegation, can be “First Time Delegator”, “Self Delegation”, “Re-Delegation” or “First Time Delegator - Self Delegation” | | NEW\_BALANCE | FLOAT | The new amount the user has delegated after the transaction | | PREVIOUS\_BALANCE | FLOAT | The amount of OP the user had delegated before the transaction | | RAW\_NEW\_BALANCE | NUMBER | The new amount the user has delegated after the transaction in raw format | | RAW\_PREVIOUS\_BALANCE | NUMBER | The amount of OP the user had delegated before the transaction in raw format | | TO\_DELEGATE | TEXT | The address of the delegate to which the delegator has delegated their votes | | FROM\_DELEGATE | TEXT | The address of the delegate from which the delegator has delegated their votes | | FACT\_DELEGATIONS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Gov](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/gov/overview) [Nft](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/overview) ⌘I --- # Ez Lending Ohlc Rates - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-lending-ohlc-rates#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Ez Lending Ohlc Rates [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-lending-ohlc-rates#columns) **Schema**: `optimism.defi` **Table**: `ez_lending_ohlc_rates` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-lending-ohlc-rates#columns) Columns ----------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | DAY | TIMESTAMP\_NTZ | | | PROTOCOL | TEXT | | | PLATFORM | TEXT | | | VERSION | TEXT | | | TOKEN\_ADDRESS | TEXT | | | TOKEN\_SYMBOL | TEXT | | | SUPPLY\_RATE\_OPEN | FLOAT | | | SUPPLY\_RATE\_HIGH | FLOAT | | | SUPPLY\_RATE\_LOW | FLOAT | | | SUPPLY\_RATE\_CLOSE | FLOAT | | | STABLE\_BORROW\_RATE\_OPEN | FLOAT | | | STABLE\_BORROW\_RATE\_HIGH | FLOAT | | | STABLE\_BORROW\_RATE\_LOW | FLOAT | | | STABLE\_BORROW\_RATE\_CLOSE | FLOAT | | | VARIABLE\_BORROW\_RATE\_OPEN | FLOAT | | | VARIABLE\_BORROW\_RATE\_HIGH | FLOAT | | | VARIABLE\_BORROW\_RATE\_LOW | FLOAT | | | VARIABLE\_BORROW\_RATE\_CLOSE | FLOAT | | | RATE\_UPDATES\_COUNT | NUMBER | | | BLOCKCHAIN | TEXT | | | EZ\_OHLC\_RATES\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | Was this page helpful? YesNo [Ez Lending Liquidations](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-lending-liquidations) [Ez Lending Repayments](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-lending-repayments) ⌘I --- # Defi - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Defi [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/overview#overview) Overview ------------------------------------------------------------------------------------------------ This schema contains 11 tables and views for Optimism data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/overview#tables-and-views) Tables and Views ---------------------------------------------------------------------------------------------------------------- [Dim Dex Liquidity Pools\ -----------------------\ \ This dimensional table contains comprehensive metadata for all DEX liquidity pools across supported protocols.](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/dim-dex-liquidity-pools) [Ez Bridge Activity\ ------------------\ \ This table provides a comprehensive view of cross-chain bridge activity across EVM-compatible blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-bridge-activity) [Ez Dex Liquidity Pool Actions\ -----------------------------\ \ This table provides a comprehensive view of liquidity pool actions across major decentralized exchanges (DEXs) on EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-dex-liquidity-pool-actions) [Ez Dex Swaps\ ------------\ \ This table provides a comprehensive view of token swap events across major decentralized exchanges (DEXs) on EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-dex-swaps) [Ez Lending Borrows\ ------------------\ \ This table provides a comprehensive view of borrowing transactions across all major lending protocols on EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-lending-borrows) [Ez Lending Deposits\ -------------------\ \ This table tracks all deposit transactions across lending protocols on EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-lending-deposits) [Ez Lending Flashloans\ ---------------------\ \ This table captures flash loan transactions across lending protocols.](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-lending-flashloans) [Ez Lending Liquidations\ -----------------------\ \ This table tracks liquidation events across lending protocols, where under-collateralized positions are forcibly closed to protect protocol solvency.](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-lending-liquidations) [Ez Lending Ohlc Rates\ ---------------------\ \ Data from Ez Lending Ohlc Rates](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-lending-ohlc-rates) [Ez Lending Repayments\ ---------------------\ \ This table contains loan repayment transactions across lending protocols.](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-lending-repayments) [Ez Lending Withdraws\ --------------------\ \ This table tracks withdrawal transactions where users remove their supplied liquidity from lending protocols.](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/ez-lending-withdraws) Was this page helpful? YesNo [Fact Transactions](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/core/fact-transactions) [Dim Dex Liquidity Pools](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/defi/dim-dex-liquidity-pools) ⌘I --- # Ez Nft Transfers - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Ez Nft Transfers [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers#commonly-used-fields) * [Sample Queries](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers#columns) **Schema**: `optimism.nft` **Table**: `ez_nft_transfers` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers#what) What ----------------------------------------------------------------------------------------------- This table contains all NFT transfer events for ERC-721 and ERC-1155 tokens on EVM blockchains. It provides a comprehensive view of NFT movements including transfers, mints, and burns, with enriched metadata for easier analysis. [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers#key-use-cases) Key Use Cases ----------------------------------------------------------------------------------------------------------------- * Track daily NFT activity and transfer volume across collections * Analyze NFT minting patterns and mint timing * Identify popular collections by transfer activity * Monitor wallet NFT accumulation and trading behavior * Analyze ERC-1155 batch transfer patterns * Track current NFT holders and ownership changes * Detect burns and unusual transfer patterns [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------- * **Join with ez\_nft\_sales**: Use `tx_hash` to match with sales but note that a single transaction can contain multiple sales. Do not use `event_index` to match as the `event_index` in ez\_nft\_transfers represent the `event_index` of the transfer and not the sale * **Join with dim\_nft\_collection\_metadata**: This is only for the Ethereum blockchain. Use `contract_address` and `token_id` for metadata like traits, token id name and token id description * **Join with fact\_transactions**: Use `tx_hash` for transaction context [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------- * `contract_address`: NFT collection contract address * `token_id`: Unique identifier of the specific NFT * `from_address` / `to_address`: Transfer participants (0x0 for mint/burn) * `is_mint`: Boolean flag for minting events * `token_standard`: NFT standard (erc721, erc1155, cryptopunks, legacy) * `nft_quantity`: Number of tokens transferred (always 1 for ERC-721) * `token_transfer_type`: Specific event type emitted [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers#sample-queries) Sample Queries ------------------------------------------------------------------------------------------------------------------- **Daily NFT Activity Overview** Copy Ask AI SELECT DATE_TRUNC('day', block_timestamp) AS day, COUNT(*) AS total_transfers, COUNT(DISTINCT contract_address) AS unique_collections, COUNT(DISTINCT CASE WHEN is_mint THEN tx_hash END) AS mint_count, COUNT(DISTINCT from_address) AS unique_senders, COUNT(DISTINCT to_address) AS unique_receivers, SUM(IFF(token_standard = 'erc721', 1 , 0)) as erc721_transfer_count, SUM(IFF(token_standard = 'erc1155', 1 , 0)) as erc1155_transfer_count FROM .nft.ez_nft_transfers WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 1 DESC; **Popular NFT Collections by Transfer Volume** Copy Ask AI SELECT contract_address, name, COUNT(*) AS transfer_count, COUNT(DISTINCT token_id) AS unique_tokens, COUNT(DISTINCT from_address) AS unique_senders, COUNT(DISTINCT to_address) AS unique_receivers, SUM(CASE WHEN is_mint THEN 1 ELSE 0 END) AS mints, SUM(CASE WHEN to_address = '0x0000000000000000000000000000000000000000' THEN 1 ELSE 0 END) AS burns FROM .nft.ez_nft_transfers WHERE block_timestamp >= CURRENT_DATE - 7 AND name IS NOT NULL GROUP BY 1, 2 ORDER BY 3 DESC LIMIT 50; **NFT Minting Analysis** Copy Ask AI SELECT contract_address, name, DATE_TRUNC('hour', block_timestamp) AS mint_hour, COUNT(*) AS mint_count, COUNT(DISTINCT to_address) AS unique_minters, COUNT(DISTINCT token_id) as unique_token_id_count FROM .nft.ez_nft_transfers WHERE is_mint = TRUE AND block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2, 3 ORDER BY 4 DESC; **Wallet NFT Activity** Copy Ask AI WITH wallet_activity AS ( SELECT address, SUM(received) AS nfts_received, SUM(sent) AS nfts_sent, SUM(received) - SUM(sent) AS net_change, COUNT(DISTINCT contract_address) AS collections_interacted FROM ( SELECT to_address AS address, COUNT(*) AS received, 0 AS sent, contract_address FROM .nft.ez_nft_transfers WHERE block_timestamp >= CURRENT_DATE - 30 AND to_address != '0x0000000000000000000000000000000000000000' GROUP BY 1, 4 UNION ALL SELECT from_address AS address, 0 AS received, COUNT(*) AS sent, contract_address FROM .nft.ez_nft_transfers WHERE block_timestamp >= CURRENT_DATE - 30 AND from_address != '0x0000000000000000000000000000000000000000' GROUP BY 1, 4 ) GROUP BY 1 ) SELECT * FROM wallet_activity WHERE collections_interacted > 5 ORDER BY net_change DESC LIMIT 100; **ERC-1155 Single and Batch Transfer Analysis** Copy Ask AI SELECT contract_address, name, token_transfer_type, COUNT(*) AS transfer_count FROM .nft.ez_nft_transfers WHERE block_timestamp >= CURRENT_DATE - 7 AND token_transfer_type in ( 'erc1155_TransferSingle', 'erc1155_TransferBatch' ) GROUP BY 1, 2, 3 ORDER BY 4 DESC; **Latest holders for a given ERC-721 collection** Copy Ask AI SELECT to_address, contract_address, token_id FROM .nft.ez_nft_transfers WHERE contract_address = '0xbd3531da5cf5857e7cfaa92426877b022e612cf8' QUALIFY ROW_NUMBER() OVER (PARTITION BY contract_address, token_id ORDER BY block_number DESC, event_index DESC) =1; [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers#columns) Columns ----------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | 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 | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | INTRA_EVENT_INDEX | NUMBER | Position within a batch transfer event, primarily for ERC-1155. Always starts with 1 for single transfers. Example: 1 | | TOKEN_TRANSFER_TYPE | TEXT | The specific event type emitted by the contract. Values include 'erc721_Transfer', 'erc1155_TransferSingle', 'erc1155_TransferBatch', etc. Example: 'erc721_Transfer' | | IS_MINT | BOOLEAN | Boolean flag indicating if this transfer is a minting event (from address is 0x0). Example: true | | FROM_ADDRESS | TEXT | The address sending/transferring the NFT. Special value of '0x0000000000000000000000000000000000000000' indicates minting event. Example: '0x1234567890123456789012345678901234567890' | | TO_ADDRESS | TEXT | The address receiving the NFT. Special value of '0x0000000000000000000000000000000000000000' indicates burning event. Example: '0x1234567890123456789012345678901234567890' | | CONTRACT_ADDRESS | TEXT | The address of the contract that emitted the NFT transfer event. Example: '0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d' | | TOKEN_ID | TEXT | The unique identifier for a specific NFT within a collection. String format to handle various token_id formats. Example: '1234' | | QUANTITY | TEXT | The number of NFTs transferred for this specific token_id. Always 1 for ERC-721, can be more for ERC-1155. Example: 1 | | TOKEN_STANDARD | TEXT | The standard of the NFT. Values include 'erc721', 'erc1155', 'cryptopunks', and 'legacy'. Example: 'erc721' | | NAME | TEXT | The name of the NFT collection. For Ethereum only, join with nft.dim_nft_collection_metadata for token-level details. Example: 'Bored Ape Yacht Club' | | ORIGIN_FUNCTION_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: - 0xa9059cbb: transfer(address,uint256) - 0x095ea7b3: approve(address,uint256) - 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | EZ\_NFT\_TRANSFERS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Nft Sales](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales) [Price](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/overview) ⌘I --- # Ez Nft Sales - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Ez Nft Sales [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales#commonly-used-fields) * [Sample Queries](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales#columns) **Schema**: `optimism.nft` **Table**: `ez_nft_sales` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales#what) What ------------------------------------------------------------------------------------------- This table provides a comprehensive view of NFT (Non-Fungible Token) sales across all major marketplaces and platforms on EVM blockchains. It captures both direct marketplace sales and aggregator-routed transactions, enabling analysis of NFT market dynamics, collection performance, and trading patterns. [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------- * Analyze daily/weekly NFT market volume and trends by platform * Track top-performing NFT collections by sales count and volume * Monitor marketplace competition and market share analysis * Identify whale activity and buyer behavior patterns * Evaluate creator royalty enforcement across platforms * Assess fee structures and revenue models by marketplace * Track cross-platform trader behavior and platform preferences [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales#important-relationships) Important Relationships --------------------------------------------------------------------------------------------------------------------------------- * Links to `core.fact_event_logs` via `tx_hash` and `event_index` * Joins with `core.dim_contracts` for collection name * References `price.ez_prices_hourly` for currency conversions * Connects to token transfer tables for ownership tracking [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales#commonly-used-fields) Commonly-used Fields --------------------------------------------------------------------------------------------------------------------------- * `platform_name`: Marketplace where sale occurred (opensea, blur, etc.) * `contract_address`: NFT collection contract address * `token_id`: Unique identifier of the specific NFT * `buyer_address` / `seller_address`: Transaction participants * `price_usd`: Sale price converted to USD (includes fees) * `total_fees_usd`: Combined platform and creator fees in USD * `event_type`: Type of sale transaction (sale, bid\_won, etc.) [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales#sample-queries) Sample Queries --------------------------------------------------------------------------------------------------------------- **Daily NFT market volume by platform** Copy Ask AI -- Daily NFT market volume by platform SELECT DATE_TRUNC('day', block_timestamp) AS date, platform_name, COUNT(*) as sales_count, COUNT(DISTINCT tx_hash) AS unique_sales_transaction_count, COUNT(DISTINCT buyer_address) AS unique_buyers, COUNT(DISTINCT contract_address) AS collections_traded, SUM(price_usd) AS total_volume_usd, AVG(price_usd) AS avg_sale_price_usd FROM .nft.ez_nft_sales WHERE block_timestamp >= CURRENT_DATE - 30 AND price_usd IS NOT NULL GROUP BY 1, 2 ORDER BY 1 DESC, 7 DESC; **Top selling NFT collections** Copy Ask AI -- Top selling NFT collections SELECT contract_address, name AS collection_name, COUNT(*) AS sales_count, COUNT(DISTINCT token_id) AS unique_tokens_sold, COUNT(DISTINCT buyer_address) AS unique_buyers, SUM(price_usd) AS total_volume_usd, AVG(price_usd) AS avg_price_usd, MAX(price_usd) AS highest_sale_usd FROM .nft.ez_nft_sales WHERE block_timestamp >= CURRENT_DATE - 7 AND price_usd IS NOT NULL GROUP BY 1, 2 ORDER BY 6 DESC LIMIT 50; **Marketplace competition analysis** Copy Ask AI -- Marketplace competition analysis WITH platform_metrics AS ( SELECT platform_name, COUNT(*) AS total_sales, SUM(price_usd) AS total_volume_usd, COUNT(DISTINCT buyer_address) AS unique_buyers, COUNT(DISTINCT seller_address) AS unique_sellers, AVG(platform_fee / NULLIF(price, 0) * 100) AS avg_platform_fee_pct, SUM(platform_fee_usd) AS total_platform_revenue_usd FROM .nft.ez_nft_sales WHERE block_timestamp >= CURRENT_DATE - 30 AND price_usd IS NOT NULL GROUP BY 1 ) SELECT platform_name, total_sales, total_volume_usd, total_volume_usd * 100.0 / SUM(total_volume_usd) OVER () AS market_share_pct, unique_buyers, unique_sellers, avg_platform_fee_pct, total_platform_revenue_usd FROM platform_metrics ORDER BY total_volume_usd DESC; **Whale activity tracking** Copy Ask AI -- Whale activity tracking WITH buyer_stats AS ( SELECT buyer_address, COUNT(*) AS purchases, COUNT(DISTINCT contract_address) AS unique_collections, SUM(price_usd) AS total_spent_usd, AVG(price_usd) AS avg_purchase_price, MAX(price_usd) AS highest_purchase FROM .nft.ez_nft_sales WHERE block_timestamp >= CURRENT_DATE - 30 AND price_usd IS NOT NULL GROUP BY 1 ) SELECT CASE WHEN total_spent_usd < 1000 THEN '< $1K' WHEN total_spent_usd < 10000 THEN '$1K - $10K' WHEN total_spent_usd < 100000 THEN '$10K - $100K' WHEN total_spent_usd < 1000000 THEN '$100K - $1M' ELSE '> $1M' END AS buyer_tier, COUNT(*) AS buyer_count, SUM(purchases) AS total_purchases, AVG(unique_collections) AS avg_collections_per_buyer, SUM(total_spent_usd) AS tier_total_spent FROM buyer_stats GROUP BY 1 ORDER BY MIN(total_spent_usd); **Creator royalty analysis** Copy Ask AI -- Creator royalty analysis SELECT name AS collection_name, contract_address, COUNT(*) AS sales_with_royalties, SUM(creator_fee) AS total_creator_fees, SUM(creator_fee_usd) AS total_creator_fees_usd, AVG(creator_fee / NULLIF(price, 0) * 100) AS avg_royalty_pct, SUM(creator_fee_usd) / NULLIF(SUM(price_usd), 0) * 100 AS effective_royalty_rate FROM .nft.ez_nft_sales WHERE creator_fee > 0 AND price > 0 AND block_timestamp >= CURRENT_DATE - 30 GROUP BY 1, 2 HAVING COUNT(*) > 10 ORDER BY total_creator_fees_usd DESC LIMIT 100; [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales#columns) Columns ------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | EVENT_TYPE | TEXT | The specific type of NFT transaction that occurred. Common values include 'sale', 'bid_won', 'redeem', and 'mint'. Example: 'sale' | | PLATFORM_ADDRESS | TEXT | The smart contract address of the marketplace facilitating the sale. Platforms may have multiple contracts for different versions. Example: '0x00000000006c3852cbef3e08e8df289169ede581' | | PLATFORM_NAME | TEXT | The marketplace or platform where the NFT sale occurred. Standardized to lowercase with no spaces. Example: 'opensea' | | PLATFORM_EXCHANGE_VERSION | TEXT | The version identifier of the marketplace contract. Tracks protocol versions and upgrades. Example: 'seaport_1_5' | | AGGREGATOR_NAME | TEXT | The NFT aggregator platform that routed the transaction. NULL indicates direct platform interaction. Example: 'gem' | | SELLER_ADDRESS | TEXT | The blockchain address that sold the NFT. Example: '0x1234567890123456789012345678901234567890' | | BUYER_ADDRESS | TEXT | The blockchain address that purchased the NFT. Example: '0x1234567890123456789012345678901234567890' | | CONTRACT_ADDRESS | TEXT | The smart contract address of the NFT collection. Supports ERC-721, ERC-1155, and custom implementations. Example: '0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d' | | NAME | TEXT | The name of the NFT collection or project. May be NULL for unverified collections. Example: 'Bored Ape Yacht Club' | | TOKEN_ID | TEXT | The unique identifier of the specific NFT within its collection. Format is numeric string. Example: '1234' | | QUANTITY | TEXT | The number of tokens sold in the transaction. Primarily relevant for ERC-1155 tokens. Example: '1' | | TOKEN_STANDARD | TEXT | The technical standard implemented by the NFT contract. Common values include 'erc721', 'erc1155', 'cryptopunks', and 'legacy'. Example: 'erc721' | | CURRENCY_SYMBOL | TEXT | The symbol of the token used for payment. Example: 'ETH' | | CURRENCY_ADDRESS | TEXT | The contract address of the payment token. Shows 'ETH' for native ETH payments. Example: '0xa0b86a33e6776a1e7f9f0b8b8b8b8b8b8b8b8b8b' | | PRICE | FLOAT | The sale price in the payment currency, including platform and creator fees. Raw price before USD conversion. Example: 2.5 | | PRICE_USD | FLOAT | The sale price converted to USD at transaction time, including platform and creator fees. May be NULL for missing price data. Example: 4250.75 | | TOTAL_FEES | FLOAT | The combined platform and creator fees in the payment currency. Example: 0.125 | | PLATFORM_FEE | FLOAT | The fee charged by the marketplace in the payment currency. Typically 2-2.5% of sale price. Example: 0.05 | | CREATOR_FEE | FLOAT | The royalty fee paid to the collection creator in the payment currency. Typically 0-10% of sale price. Example: 0.075 | | TOTAL_FEES_USD | FLOAT | The combined platform and creator fees converted to USD. Example: 212.54 | | PLATFORM_FEE_USD | FLOAT | The marketplace fee converted to USD. Example: 85.02 | | CREATOR_FEE_USD | FLOAT | The royalty fee converted to USD. Example: 127.52 | | TX_FEE | FLOAT | Total fee paid for transaction execution in native token units. Example: 0.002 | | TX_FEE_USD | FLOAT | The transaction fee denominated in USD. Use only one instance per transaction to avoid overcounting. Example: 45.32 | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: * 0xa9059cbb: transfer(address,uint256) * 0x095ea7b3: approve(address,uint256) * 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | EZ\_NFT\_SALES\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Nft](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/overview) [Ez Nft Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers) ⌘I --- # Nft - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Nft [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/overview#overview) Overview ----------------------------------------------------------------------------------------------- This schema contains 2 tables and views for Optimism data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/overview#tables-and-views) Tables and Views --------------------------------------------------------------------------------------------------------------- [Ez Nft Sales\ ------------\ \ This table provides a comprehensive view of NFT (Non-Fungible Token) sales across all major marketplaces and platforms on EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales) [Ez Nft Transfers\ ----------------\ \ This table contains all NFT transfer events for ERC-721 and ERC-1155 tokens on EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-transfers) Was this page helpful? YesNo [Fact Delegations](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/gov/fact-delegations) [Ez Nft Sales](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/nft/ez-nft-sales) ⌘I --- # Dim Asset Metadata - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/dim-asset-metadata#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Dim Asset Metadata [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/dim-asset-metadata#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/dim-asset-metadata#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/dim-asset-metadata#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/dim-asset-metadata#commonly-used-fields) * [Sample Queries](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/dim-asset-metadata#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/dim-asset-metadata#columns) **Schema**: `optimism.price` **Table**: `dim_asset_metadata` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/dim-asset-metadata#what) What --------------------------------------------------------------------------------------------------- This table provides comprehensive metadata for all assets (tokens and native assets) tracked in the price schema across EVM blockchains. It includes provider, asset identifiers, names, symbols, contract addresses, blockchain, and verification status. [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/dim-asset-metadata#key-use-cases) Key Use Cases --------------------------------------------------------------------------------------------------------------------- * Join price data to asset metadata for enriched analysis * Cross-chain asset analysis and mapping * Asset discovery and verification status checking * Provider-specific data source analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/dim-asset-metadata#important-relationships) Important Relationships ----------------------------------------------------------------------------------------------------------------------------------------- * **Join with ez\_prices\_hourly**: For price time series data * **Join with core.dim\_contracts**: For contract metadata [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/dim-asset-metadata#commonly-used-fields) Commonly-used Fields ----------------------------------------------------------------------------------------------------------------------------------- * `provider`: Data source (coingecko, coinmarketcap, etc.) * `asset_id`: Provider-specific unique identifier * `blockchain`: Network identifier * `token_address`: Contract address (NULL for native assets) * `symbol`: Token ticker symbol * `name`: Full asset name [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/dim-asset-metadata#sample-queries) Sample Queries ----------------------------------------------------------------------------------------------------------------------- **Basic Asset Lookup** Copy Ask AI SELECT * FROM .price.dim_asset_metadata WHERE blockchain = 'ethereum' ORDER BY symbol; [​](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/dim-asset-metadata#columns) Columns --------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | TOKEN\_ADDRESS | TEXT | Contract address of the token on the blockchain. NULL for native assets (ETH, AVAX, etc.). | Example: ‘0xa0b86a33e6776a1e7f9f0b8b8b8b8b8b8b8b8b8b’ | | ASSET\_ID | TEXT | Unique identifier for the asset from the price provider. Provider-specific ID format. Example: ‘ethereum’ | | SYMBOL | TEXT | Token ticker symbol as commonly recognized. Usually 3-5 uppercase characters. Example: ‘WETH’ | | NAME | TEXT | Full name of the asset or token. More descriptive than symbol. Example: ‘Wrapped Ether’ | | BLOCKCHAIN | TEXT | The blockchain network where the asset exists. Lowercase by convention. Example: ‘ethereum’ | | BLOCKCHAIN\_ID | TEXT | The numeric or string identifier for the blockchain on which the asset exists. Used for cross-chain mapping. Example: ‘1’ | | PROVIDER | TEXT | Data source that provided the price information. Values include ‘coingecko’, ‘coinmarketcap’, ‘dex\_aggregated’. Example: ‘coingecko’ | | DIM\_ASSET\_METADATA\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Price](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/overview) [Ez Asset Metadata](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/price/ez-asset-metadata) ⌘I --- # Fact Governance Proposal Deposits - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-proposal-deposits#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Gov Fact Governance Proposal Deposits [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-proposal-deposits#columns) **Schema**: `osmosis.gov` **Table**: `fact_governance_proposal_deposits` **Type**: View Records of all proposal deposits that have occurred on Osmosis, dating back to the genesis block. At least 500 OSMO must be deposited for a proposal to be voted on. [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-proposal-deposits#columns) Columns --------------------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_ID | NUMBER | The block height the block was recorded at. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The date and time at which the block began. | | TX\_ID | TEXT | A unique key that identifies a transaction. Called “TxHash” on block explorers. | | TX\_SUCCEEDED | BOOLEAN | Transaction status is “TRUE” if the transaction was successful, “FALSE” if the transaction failed. | | DEPOSITOR | TEXT | The wallet address of the individual who deposited funds into the proposal. At least 500 OSMO must be deposited into a proposal after it is submitted for it to go to vote. | | PROPOSAL\_ID | NUMBER | Numeric ID that corresponds to the proposal. | | AMOUNT | FLOAT | The amount that was used in the transaction message. | | CURRENCY | TEXT | The currency that was used in the transaction message. | | DECIMAL | NUMBER | Divide the amount by POW(10, decimal) to get the amount used in the transaction. This value can be NULL, as decimals are hand curated from an outside source and not found on-chain. | | FACT\_GOVERNANCE\_PROPOSAL\_DEPOSITS\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | Was this page helpful? YesNo [Dim Vote Options](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/dim-vote-options) [Fact Governance Submit Proposal](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-submit-proposal) ⌘I --- # Fact Governance Submit Proposal - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-submit-proposal#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Gov Fact Governance Submit Proposal [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-submit-proposal#columns) **Schema**: `osmosis.gov` **Table**: `fact_governance_submit_proposal` **Type**: View Records of all proposal submissions on Osmosis, dating back to the Genesis block. [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-submit-proposal#columns) Columns ------------------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_ID | NUMBER | The block height the block was recorded at. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The date and time at which the block began. | | TX\_ID | TEXT | A unique key that identifies a transaction. Called “TxHash” on block explorers. | | TX\_SUCCEEDED | BOOLEAN | Transaction status is “TRUE” if the transaction was successful, “FALSE” if the transaction failed. | | PROPOSER | TEXT | The address of the validator that submitted the proposal. | | PROPOSAL\_ID | NUMBER | Numeric ID that corresponds to the proposal. | | PROPOSAL\_TYPE | TEXT | The type of proposal that was submitted. | | PROPOSAL\_TITLE | TEXT | The title of the governance proposal that was submitted on-chain. | | PROPOSAL\_DESCRIPTION | TEXT | The description or body of the governance proposal. | | FACT\_GOVERNANCE\_SUBMIT\_PROPOSAL\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | Was this page helpful? YesNo [Fact Governance Proposal Deposits](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-proposal-deposits) [Fact Governance Votes](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-votes) ⌘I --- # Fact Governance Votes - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-votes#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Gov Fact Governance Votes [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-votes#columns) **Schema**: `osmosis.gov` **Table**: `fact_governance_votes` **Type**: View Records of all votes on proposals. [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-votes#columns) Columns --------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_ID | NUMBER | The block height the block was recorded at. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | The date and time at which the block began. | | TX\_ID | TEXT | A unique key that identifies a transaction. Called “TxHash” on block explorers. | | TX\_SUCCEEDED | BOOLEAN | Transaction status is “TRUE” if the transaction was successful, “FALSE” if the transaction failed. | | VOTER | TEXT | Address of the delegator that voted on the proposal. | | PROPOSAL\_ID | NUMBER | Numeric ID that corresponds to the proposal. | | VOTE\_OPTION | VARIANT | How the delegator voted on the proposal. | | VOTE\_WEIGHT | FLOAT | | | FACT\_GOVERNANCE\_VOTES\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | Was this page helpful? YesNo [Fact Governance Submit Proposal](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-submit-proposal) [Price](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/overview) ⌘I --- # Gov - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Gov Gov [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/overview#overview) Overview ---------------------------------------------------------------------------------------------- This schema contains 4 tables and views for Osmosis data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/overview#tables-and-views) Tables and Views -------------------------------------------------------------------------------------------------------------- [Dim Vote Options\ ----------------\ \ Table that contains the vote options for governance proposals.](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/dim-vote-options) [Fact Governance Proposal Deposits\ ---------------------------------\ \ Records of all proposal deposits that have occurred on Osmosis, dating back to the genesis block.](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-proposal-deposits) [Fact Governance Submit Proposal\ -------------------------------\ \ Records of all proposal submissions on Osmosis, dating back to the Genesis block.](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-submit-proposal) [Fact Governance Votes\ ---------------------\ \ Records of all votes on proposals.](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-votes) Was this page helpful? YesNo [Fact Swaps](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/defi/fact-swaps) [Dim Vote Options](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/dim-vote-options) ⌘I --- # Dim Prices - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/dim-prices#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Dim Prices [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/dim-prices#columns) **Schema**: `osmosis.price` **Table**: `dim_prices` **Type**: View Contains token prices in USD for assets that can be traded on the Osmosis Zone and Frontier. [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/dim-prices#columns) Columns ------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | RECORDED\_AT | TIMESTAMP\_NTZ | The time, including the day and hour, that the price of the token corresponds to. | | SYMBOL | TEXT | The token’s symbol | | CURRENCY | TEXT | | | PRICE | FLOAT | The price of the token in USD. | | TOTAL\_SUPPLY | TEXT | The total circulating supply of the token | | VOLUME\_24H | TEXT | | | PROVIDER | TEXT | Where the price is sourced from. Prices sourced from the swaps table may have outliers for hours with low swap volume. | | DIM\_PRICES\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | Was this page helpful? YesNo [Price](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/overview) [Ez Prices](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/ez-prices) ⌘I --- # Osmosis Data - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Osmosis Osmosis Data [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/overview#overview) * [Available Schemas](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/overview#available-schemas) [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/overview#overview) Overview ------------------------------------------------------------------------------------------ This section contains comprehensive documentation for all Osmosis data available through Flipside Crypto.[View DBT Documentation\ ----------------------\ \ View the complete technical documentation and data lineage for Osmosis models](https://flipsidecrypto.github.io/osmosis-models/) [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/overview#available-schemas) Available Schemas ------------------------------------------------------------------------------------------------------------ [Core Tables\ -----------\ \ Tables and views in the osmosis.core schema](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/core/overview) [Defi\ ----\ \ Tables and views in the osmosis.defi schema](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/defi/overview) [Gov\ ---\ \ Tables and views in the osmosis.gov schema](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/overview) [Price\ -----\ \ Tables and views in the osmosis.price schema](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/overview) [Stats\ -----\ \ Tables and views in the osmosis.stats schema](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/stats/overview) Was this page helpful? YesNo [Ez Core Metrics Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/optimism/stats/ez-core-metrics-hourly) [Core Tables](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/core/overview) ⌘I --- # Ez Prices - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/ez-prices#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Ez Prices [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/ez-prices#columns) **Schema**: `osmosis.price` **Table**: `ez_prices` **Type**: View Contains token prices in USD for assets that can be traded on Osmosis. [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/ez-prices#columns) Columns ----------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | RECORDED\_HOUR | TIMESTAMP\_NTZ | The time, including the day and hour, that the price of the token corresponds to. | | SYMBOL | TEXT | The token’s symbol | | CURRENCY | TEXT | The currency that was used in the transaction message. | | PRICE | FLOAT | The price of the token in USD. | | EZ\_PRICES\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | Was this page helpful? YesNo [Dim Prices](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/dim-prices) [Stats](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/stats/overview) ⌘I --- # Price - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Price Price [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/overview#overview) Overview ------------------------------------------------------------------------------------------------ This schema contains 2 tables and views for Osmosis data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/overview#tables-and-views) Tables and Views ---------------------------------------------------------------------------------------------------------------- [Dim Prices\ ----------\ \ Contains token prices in USD for assets that can be traded on the Osmosis Zone and Frontier.](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/dim-prices) [Ez Prices\ ---------\ \ Contains token prices in USD for assets that can be traded on Osmosis.](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/ez-prices) Was this page helpful? YesNo [Fact Governance Votes](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/gov/fact-governance-votes) [Dim Prices](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/dim-prices) ⌘I --- # Ez Core Metrics Hourly - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/stats/ez-core-metrics-hourly#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Stats Ez Core Metrics Hourly [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/stats/ez-core-metrics-hourly#columns) **Schema**: `osmosis.stats` **Table**: `ez_core_metrics_hourly` **Type**: View A convenience table that aggregates block and transaction related metrics using various aggregate functions such as SUM, COUNT, MIN and MAX from the fact\_transactions table, on an hourly basis. Stats for the current hour will be updated as new data arrives. [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/stats/ez-core-metrics-hourly#columns) Columns ------------------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_TIMESTAMP\_HOUR | TIMESTAMP\_NTZ | The hour of the timestamp of the block. | | BLOCK\_NUMBER\_MIN | NUMBER | The minimum block id in the hour. | | BLOCK\_NUMBER\_MAX | NUMBER | The maximum block id in the hour. | | BLOCK\_COUNT | NUMBER | The number of blocks in the hour. | | TRANSACTION\_COUNT | NUMBER | The number of transactions in the hour. | | TRANSACTION\_COUNT\_SUCCESS | NUMBER | The number of successful transactions in the hour. | | TRANSACTION\_COUNT\_FAILED | NUMBER | The number of failed transactions in the hour. | | UNIQUE\_FROM\_COUNT | NUMBER | The number of unique tx\_from addresses in the hour. | | TOTAL\_FEES\_NATIVE | FLOAT | The sum of all fees in the hour, in the native fee currency. | | TOTAL\_FEES\_USD | FLOAT | The sum of all fees in the hour, in USD. | | EZ\_CORE\_METRICS\_HOURLY\_ID | TEXT | The unique identifier for each row in the table. | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was inserted into the table. | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | The utc timestamp at which the row was last modified. | Was this page helpful? YesNo [Stats](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/stats/overview) [Polygon Data](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/overview) ⌘I --- # Stats - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/stats/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Stats Stats [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/stats/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/stats/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/stats/overview#overview) Overview ------------------------------------------------------------------------------------------------ This schema contains 1 tables and views for Osmosis data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/stats/overview#tables-and-views) Tables and Views ---------------------------------------------------------------------------------------------------------------- [Ez Core Metrics Hourly\ ----------------------\ \ A convenience table that aggregates block and transaction related metrics using various aggregate functions such as SUM, COUNT, MIN and MAX from th…](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/stats/ez-core-metrics-hourly) Was this page helpful? YesNo [Ez Prices](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/price/ez-prices) [Ez Core Metrics Hourly](https://docs.flipsidecrypto.xyz/blockchain-data/osmosis/stats/ez-core-metrics-hourly) ⌘I --- # Balances - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Balances Balances [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/overview#overview) Overview --------------------------------------------------------------------------------------------------- This schema contains 2 tables and views for Polygon data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/overview#tables-and-views) Tables and Views ------------------------------------------------------------------------------------------------------------------- [Ez Balances Erc20 Daily\ -----------------------\ \ This table provides daily ERC20 token balance snapshots for verified token contracts by making direct balanceOf contract calls at the end of each day.](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily) [Ez Balances Native Daily\ ------------------------\ \ This table provides daily native asset balance snapshots (ETH, AVAX, BNB, etc.) by making direct eth\_getBalance RPC calls at the end of each day.](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily) Was this page helpful? YesNo [Polygon Data](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/overview) [Ez Balances Erc20 Daily](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily) ⌘I --- # Ez Balances Erc20 Daily - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Balances Ez Balances Erc20 Daily [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily#columns) **Schema**: `polygon.balances` **Table**: `ez_balances_erc20_daily` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily#what) What ---------------------------------------------------------------------------------------------------------- This table provides daily ERC20 token balance snapshots for verified token contracts by making direct `balanceOf` contract calls at the end of each day. It captures the current token balance for each address-token pair that has had transfer activity, providing a comprehensive view of token holdings across all verified ERC20 tokens with decimal adjustments and USD valuations where available. Historical ERC20 balances data available, starting from `2025-06-10`. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily#key-use-cases) Key Use Cases ---------------------------------------------------------------------------------------------------------------------------- * Daily portfolio tracking and balance monitoring for ERC20 tokens * Historical balance analysis and trend identification * Token holder distribution analysis at daily granularity * Wallet balance snapshots for reporting and analytics * Cross-token balance comparisons and concentration analysis * Token supply distribution monitoring over time * Daily balance-based yield and return calculations [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------------------ * **Join with fact\_blocks**: Use `block_number` for block metadata and timestamps * **Join with dim\_labels**: Use `address` for entity identification and categorization * **Join with dim\_contracts**: Use `contract_address` for token contract details * **Join with ez\_prices\_hourly**: USD valuations already included but can be refreshed * **Join with ez\_balances\_native\_daily**: Compare with native token daily balances * **Join with ez\_token\_transfers**: Compare daily balances with transfer activity [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------------------ * `address`: The account address holding the token balance * `contract_address`: The ERC20 token contract address * `symbol`: Token symbol (USDC, WETH, etc.) * `balance`: Token balance at end of day, decimal adjusted to standard units * `balance_usd`: USD value of the token balance at end of day * `balance_raw`: Raw balance in smallest token unit (wei equivalent) * `balance_precise`: Precise decimal-adjusted balance as string * `decimals`: Number of decimal places for the token * `block_date`: The date for which this balance snapshot was taken [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily#sample-queries) Sample queries ------------------------------------------------------------------------------------------------------------------------------ **Daily Token Holdings by Address** Copy Ask AI SELECT block_date, address, symbol, balance, balance_usd, contract_address FROM .balances.ez_balances_erc20_daily WHERE address = LOWER('0x1234567890123456789012345678901234567890') AND block_date >= CURRENT_DATE - 30 AND balance > 0 ORDER BY block_date DESC, balance_usd DESC; **Token Holder Count Trends** Copy Ask AI SELECT block_date, symbol, contract_address, COUNT(DISTINCT address) AS holder_count, SUM(balance) AS total_supply_tracked, AVG(balance) AS avg_balance, MEDIAN(balance) AS median_balance FROM .balances.ez_balances_erc20_daily WHERE block_date >= CURRENT_DATE - 90 AND balance > 0 AND symbol IS NOT NULL GROUP BY 1, 2, 3 ORDER BY 1 DESC, holder_count DESC; **Portfolio Value Evolution** Copy Ask AI -- Track portfolio value changes over time for specific addresses SELECT block_date, address, COUNT(DISTINCT contract_address) AS token_count, SUM(balance_usd) AS total_portfolio_usd, STRING_AGG( CASE WHEN balance_usd > 100 THEN symbol || ': $' || ROUND(balance_usd, 2) END, ', ' ) AS major_holdings FROM .balances.ez_balances_erc20_daily WHERE address IN ( SELECT DISTINCT address FROM .balances.ez_balances_erc20_daily WHERE balance_usd > 10000 LIMIT 100 ) AND block_date >= CURRENT_DATE - 30 AND balance > 0 GROUP BY 1, 2 HAVING total_portfolio_usd > 1000 ORDER BY 1 DESC, total_portfolio_usd DESC; **Token Distribution Analysis** Copy Ask AI -- Analyze token concentration and distribution patterns SELECT symbol, contract_address, block_date, COUNT(DISTINCT address) AS total_holders, COUNT(DISTINCT CASE WHEN balance >= 1000 THEN address END) AS holders_1k_plus, COUNT(DISTINCT CASE WHEN balance >= 10000 THEN address END) AS holders_10k_plus, MAX(balance) AS max_balance, PERCENTILE_CONT(0.95) WITHIN GROUP (ORDER BY balance) AS p95_balance, PERCENTILE_CONT(0.50) WITHIN GROUP (ORDER BY balance) AS median_balance FROM .balances.ez_balances_erc20_daily WHERE block_date = CURRENT_DATE - 1 AND balance > 0 AND symbol IS NOT NULL GROUP BY 1, 2, 3 HAVING total_holders >= 100 ORDER BY total_holders DESC LIMIT 50; **Daily Balance Changes** Copy Ask AI -- Compare daily balances to identify significant changes WITH daily_changes AS ( SELECT address, contract_address, symbol, block_date, balance, balance_usd, LAG(balance) OVER ( PARTITION BY address, contract_address ORDER BY block_date ) AS prev_balance, LAG(balance_usd) OVER ( PARTITION BY address, contract_address ORDER BY block_date ) AS prev_balance_usd FROM .balances.ez_balances_erc20_daily WHERE block_date >= CURRENT_DATE - 7 AND balance > 0 ) SELECT block_date, address, symbol, balance, prev_balance, balance - prev_balance AS balance_change, balance_usd - prev_balance_usd AS balance_change_usd, CASE WHEN prev_balance > 0 THEN ((balance - prev_balance) / prev_balance) * 100 ELSE NULL END AS pct_change FROM daily_changes WHERE ABS(balance_change_usd) > 1000 AND prev_balance IS NOT NULL ORDER BY ABS(balance_change_usd) DESC LIMIT 100; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily#columns) Columns ---------------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_DATE | DATE | The date for which this balance snapshot represents the end-of-day token balance. Example: ‘2025-07-04’ | | ADDRESS | TEXT | The account address whose token balance is recorded in this daily snapshot. Example: ‘0x1234567890123456789012345678901234567890’ | | CONTRACT\_ADDRESS | TEXT | The ERC20 token contract address for which the balance is recorded. Example: ‘0xa0b86a33e6eb88b4d81b15e4e60c8a5b776e3b7a’ | | DECIMALS | NUMBER | Number of decimal places for the token, used for proper decimal adjustment in balance calculations. Example: 6 | | SYMBOL | TEXT | The token symbol for the ERC20 token. Example: ‘USDC’ | | BALANCE\_HEX | TEXT | Hexadecimal representation of the token balance as returned by the balanceOf contract call. Example: ‘0x3b9aca00’ | | BALANCE\_RAW | NUMBER | Token balance in the smallest unit (wei equivalent) without decimal adjustment, as returned by the contract. Example: 1000000000 | | BALANCE\_PRECISE | TEXT | Token balance with proper decimal adjustment, returned as a string to preserve precision. Example: ‘1000.000000’ | | BALANCE | FLOAT | Token balance with decimal adjustment converted to a float for easier mathematical operations. Example: 1000.0 | | BALANCE\_USD | FLOAT | USD value of the token balance at the end of the day, calculated using hourly price data. Example: 1000.50 | | EZ\_BALANCES\_ERC20\_DAILY\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Balances](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/overview) [Ez Balances Native Daily](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily) ⌘I --- # Dim Contract Abis - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Dim Contract Abis [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis#columns) **Schema**: `polygon.core` **Table**: `dim_contract_abis` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis#what) What ------------------------------------------------------------------------------------------------ This table contains Application Binary Interfaces (ABIs) for smart contracts deployed on EVM blockchains. ABIs define the contract’s functions, events, and data structures, enabling the decoding of raw blockchain data into human-readable format. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------------ * Decoding raw event logs into human-readable format * Identifying contract functions and their parameters * Enabling interaction with smart contracts programmatically * Analyzing contract patterns and implementations across chains * Supporting automated contract verification and bytecode matching [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis#important-relationships) Important Relationships -------------------------------------------------------------------------------------------------------------------------------------- * **Powers ez\_decoded\_event\_logs**: ABIs enable event decoding * **Join with dim\_contracts**: Use `contract_address` for contract metadata * **Enables fact\_decoded\_event\_logs**: Raw to decoded transformation [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis#commonly-used-fields) Commonly-used Fields -------------------------------------------------------------------------------------------------------------------------------- * `contract_address`: The contract’s blockchain address * `abi`: The contract’s Application Binary Interface in JSON format * `abi_source`: The origin of the ABI data (explorer verified, user submitted, bytecode matched) * `bytecode`: The compiled contract code deployed on-chain * `created_timestamp`: When the ABI was added to the database [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis#sample-queries) Sample queries -------------------------------------------------------------------------------------------------------------------- **Find Contracts Without ABIs** Copy Ask AI -- Identify popular contracts needing ABIs WITH contract_activity AS ( SELECT contract_address, COUNT(*) AS event_count FROM .core.fact_event_logs WHERE block_timestamp >= CURRENT_DATE - 7 GROUP BY 1 ) SELECT ca.contract_address, c.name AS contract_name, ca.event_count, c.created_block_timestamp FROM contract_activity ca LEFT JOIN .core.dim_contract_abis abi ON ca.contract_address = abi.contract_address LEFT JOIN .core.dim_contracts c ON ca.contract_address = c.address WHERE abi.abi IS NULL OR abi.abi = '[]' ORDER BY ca.event_count DESC LIMIT 100; **Analyze ABI Functions and Events** Copy Ask AI -- Extract event signatures from ABIs WITH abi_events AS ( SELECT contract_address, abi_source, f.value:name::string AS event_name, f.value:type::string AS entry_type FROM .core.dim_contract_abis, LATERAL FLATTEN(input => PARSE_JSON(abi)) f WHERE f.value:type::string = 'event' AND abi IS NOT NULL ) SELECT event_name, COUNT(DISTINCT contract_address) AS contracts_with_event, ARRAY_AGG(DISTINCT abi_source) AS sources FROM abi_events GROUP BY 1 ORDER BY 2 DESC LIMIT 50; **Bytecode Matching Effectiveness** Copy Ask AI -- Analyze bytecode matching success SELECT DATE_TRUNC('week', created_timestamp) AS week, COUNT(CASE WHEN abi_source = 'bytecode_matched' THEN 1 END) AS bytecode_matched, COUNT(CASE WHEN abi_source = 'user_submitted' THEN 1 END) AS user_submitted, COUNT(CASE WHEN abi_source LIKE '%explorer%' THEN 1 END) AS explorer_verified, COUNT(*) AS total_new_abis FROM .core.dim_contract_abis WHERE created_timestamp >= CURRENT_DATE - 90 GROUP BY 1 ORDER BY 1 DESC; **Common Contract Patterns** Copy Ask AI -- Find contracts sharing bytecode (proxy patterns, clones) WITH bytecode_groups AS ( SELECT bytecode, COUNT(DISTINCT contract_address) AS contract_count, ARRAY_AGG(DISTINCT contract_address) AS contracts, MAX(abi) AS sample_abi FROM .core.dim_contract_abis WHERE bytecode IS NOT NULL AND LENGTH(bytecode) > 100 -- Exclude minimal contracts GROUP BY 1 HAVING COUNT(DISTINCT contract_address) > 5 ) SELECT contract_count, ARRAY_SIZE(contracts) AS unique_addresses, LEFT(bytecode, 20) || '...' AS bytecode_prefix, CASE WHEN sample_abi LIKE '%proxy%' THEN 'Likely Proxy' WHEN sample_abi LIKE '%clone%' THEN 'Likely Clone' ELSE 'Standard Pattern' END AS pattern_type FROM bytecode_groups ORDER BY contract_count DESC LIMIT 20; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis#columns) Columns ------------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | CONTRACT\_ADDRESS | TEXT | Unique identifier - the deployed contract’s blockchain address. | Example: ‘0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48’ | | ABI | VARIANT | The contract’s Application Binary Interface in JSON format, containing function and event definitions that enable interaction with the smart contract. Example: `'[{"name":"transfer","type":"function","inputs":[{"name":"to","type":"address"},{"name":"value","type":"uint256"}],"outputs":[{"name":"","type":"bool"}]}]'` | | ABI\_SOURCE | TEXT | The origin of the ABI data, indicating trust level and collection method. Example: ‘etherscan’ | | BYTECODE | TEXT | The compiled contract code deployed on-chain, used for bytecode matching and identifying identical contracts. Example: ‘0x608060405234801561001057600080fd5b50…’ | | DIM\_CONTRACT\_ABIS\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | Was this page helpful? YesNo [Core Tables](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/overview) [Dim Contracts](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts) ⌘I --- # Ez Balances Native Daily - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Balances Ez Balances Native Daily [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily#columns) **Schema**: `polygon.balances` **Table**: `ez_balances_native_daily` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily#what) What ----------------------------------------------------------------------------------------------------------- This table provides daily native asset balance snapshots (ETH, AVAX, BNB, etc.) by making direct `eth_getBalance` RPC calls at the end of each day. It captures the current native asset balance for each address that has had native asset activity, providing a comprehensive view of native holdings with decimal adjustments and USD valuations where available. Historical native balances data available, starting from `2025-06-10`. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily#key-use-cases) Key Use Cases ----------------------------------------------------------------------------------------------------------------------------- * Daily portfolio tracking and native asset balance monitoring * Historical native asset balance analysis and trend identification * Whale tracking and large holder distribution analysis * Daily balance snapshots for reporting and analytics * Native asset concentration analysis across addresses * Daily balance-based yield and return calculations for native assets * End-of-day balance reconciliation and accounting [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------------------- * **Join with fact\_blocks**: Use `block_number` for block metadata and timestamps * **Join with dim\_labels**: Use `address` for entity identification and categorization * **Join with ez\_prices\_hourly**: USD valuations already included but can be refreshed * **Join with ez\_balances\_erc20\_daily**: Compare with ERC20 token daily balances * **Join with ez\_native\_transfers**: Compare daily balances with transfer activity * **Join with core\_\_fact\_traces**: Analyze native asset movement patterns [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------------------- * `address`: The account address holding the native asset balance * `balance`: Native asset balance at end of day, decimal adjusted to standard units * `balance_usd`: USD value of the native asset balance at end of day * `balance_raw`: Raw balance in smallest unit (Wei) without decimal adjustment * `balance_precise`: Precise decimal-adjusted balance as string * `balance_hex`: Hexadecimal balance as returned by eth\_getBalance * `decimals`: Number of decimal places (always 18 for native assets) * `block_date`: The date for which this balance snapshot was taken [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily#sample-queries) Sample queries ------------------------------------------------------------------------------------------------------------------------------- **Daily Native Asset Holdings by Address** Copy Ask AI SELECT block_date, address, balance, balance_usd, LAG(balance) OVER ( PARTITION BY address ORDER BY block_date ) AS prev_balance, balance - LAG(balance) OVER ( PARTITION BY address ORDER BY block_date ) AS daily_change FROM .balances.ez_balances_native_daily WHERE address = LOWER('0x1234567890123456789012345678901234567890') AND block_date >= CURRENT_DATE - 30 AND balance > 0 ORDER BY block_date DESC; **Native Asset Holder Distribution Trends** Copy Ask AI SELECT block_date, COUNT(DISTINCT address) AS total_holders, COUNT(DISTINCT CASE WHEN balance >= 1 THEN address END) AS holders_1_plus, COUNT(DISTINCT CASE WHEN balance >= 10 THEN address END) AS holders_10_plus, COUNT(DISTINCT CASE WHEN balance >= 100 THEN address END) AS holders_100_plus, COUNT(DISTINCT CASE WHEN balance >= 1000 THEN address END) AS holders_1000_plus, SUM(balance) AS total_native_tracked, AVG(balance) AS avg_balance, MEDIAN(balance) AS median_balance, MAX(balance) AS max_balance FROM .balances.ez_balances_native_daily WHERE block_date >= CURRENT_DATE - 90 AND balance > 0 GROUP BY 1 ORDER BY 1 DESC; **Whale Activity Monitoring** Copy Ask AI -- Track large native asset holders and their balance changes WITH whale_balances AS ( SELECT address, block_date, balance, balance_usd, LAG(balance) OVER ( PARTITION BY address ORDER BY block_date ) AS prev_balance, LAG(balance_usd) OVER ( PARTITION BY address ORDER BY block_date ) AS prev_balance_usd FROM .balances.ez_balances_native_daily WHERE balance >= 1000 -- Focus on large holders AND block_date >= CURRENT_DATE - 7 ), whale_changes AS ( SELECT *, balance - prev_balance AS balance_change, balance_usd - prev_balance_usd AS balance_change_usd, CASE WHEN prev_balance > 0 THEN ((balance - prev_balance) / prev_balance) * 100 ELSE NULL END AS pct_change FROM whale_balances WHERE prev_balance IS NOT NULL ) SELECT block_date, address, balance, balance_change, balance_change_usd, pct_change, CASE WHEN balance_change > 100 THEN 'Large Increase' WHEN balance_change > 10 THEN 'Moderate Increase' WHEN balance_change < -100 THEN 'Large Decrease' WHEN balance_change < -10 THEN 'Moderate Decrease' ELSE 'Stable' END AS change_category FROM whale_changes WHERE ABS(balance_change) > 5 -- Only show meaningful changes ORDER BY ABS(balance_change_usd) DESC LIMIT 100; **Daily Balance Distribution Analysis** Copy Ask AI -- Analyze the distribution of native asset balances SELECT block_date, CASE WHEN balance < 0.001 THEN 'Dust (<0.001)' WHEN balance < 0.01 THEN 'Very Small (0.001-0.01)' WHEN balance < 0.1 THEN 'Small (0.01-0.1)' WHEN balance < 1 THEN 'Medium (0.1-1)' WHEN balance < 10 THEN 'Large (1-10)' WHEN balance < 100 THEN 'Very Large (10-100)' WHEN balance < 1000 THEN 'Whale (100-1000)' ELSE 'Super Whale (1000+)' END AS balance_category, COUNT(DISTINCT address) AS address_count, SUM(balance) AS total_balance, SUM(balance_usd) AS total_balance_usd, AVG(balance) AS avg_balance, PERCENTILE_CONT(0.5) WITHIN GROUP (ORDER BY balance) AS median_balance FROM .balances.ez_balances_native_daily WHERE block_date = CURRENT_DATE - 1 AND balance > 0 GROUP BY 1, 2 ORDER BY 1 DESC, CASE balance_category WHEN 'Dust (<0.001)' THEN 1 WHEN 'Very Small (0.001-0.01)' THEN 2 WHEN 'Small (0.01-0.1)' THEN 3 WHEN 'Medium (0.1-1)' THEN 4 WHEN 'Large (1-10)' THEN 5 WHEN 'Very Large (10-100)' THEN 6 WHEN 'Whale (100-1000)' THEN 7 WHEN 'Super Whale (1000+)' THEN 8 END; **Portfolio Value Evolution** Copy Ask AI -- Track total portfolio value changes for top holders SELECT block_date, COUNT(DISTINCT address) AS tracked_addresses, SUM(balance_usd) AS total_portfolio_value, AVG(balance_usd) AS avg_portfolio_value, SUM(balance) AS total_native_balance, LAG(SUM(balance_usd)) OVER (ORDER BY block_date) AS prev_total_value, (SUM(balance_usd) - LAG(SUM(balance_usd)) OVER (ORDER BY block_date)) AS daily_value_change, CASE WHEN LAG(SUM(balance_usd)) OVER (ORDER BY block_date) > 0 THEN ((SUM(balance_usd) - LAG(SUM(balance_usd)) OVER (ORDER BY block_date)) / LAG(SUM(balance_usd)) OVER (ORDER BY block_date)) * 100 ELSE NULL END AS daily_pct_change FROM .balances.ez_balances_native_daily WHERE block_date >= CURRENT_DATE - 30 AND balance_usd >= 10000 -- Focus on significant holders GROUP BY 1 ORDER BY 1 DESC; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily#columns) Columns ----------------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_DATE | DATE | The date for which this balance snapshot represents the end-of-day native asset balance. Example: ‘2023-12-15’ | | ADDRESS | TEXT | The account address whose native asset balance is recorded in this daily snapshot. Example: ‘0x1234567890123456789012345678901234567890’ | | DECIMALS | NUMBER | | | BALANCE\_HEX | TEXT | Hexadecimal representation of the native asset balance as returned by the eth\_getBalance RPC call. Example: ‘0x3b9aca00’ | | BALANCE\_RAW | NUMBER | Native asset balance in the smallest unit (Wei) without decimal adjustment, as returned by eth\_getBalance. Example: 1000000000000000000 | | BALANCE\_PRECISE | TEXT | Native asset balance with proper decimal adjustment, returned as a string to preserve precision. Example: ‘1.000000000000000000’ | | BALANCE | FLOAT | Native asset balance with decimal adjustment converted to a float for easier mathematical operations. Example: 1.0 | | BALANCE\_USD | FLOAT | USD value of the native asset balance at the end of the day, calculated using hourly price data. Example: 2500.75 | | EZ\_BALANCES\_NATIVE\_DAILY\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Balances Erc20 Daily](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-erc20-daily) [Core Tables](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/overview) ⌘I --- # Dim Contracts - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Dim Contracts [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts#columns) **Schema**: `polygon.core` **Table**: `dim_contracts` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts#what) What -------------------------------------------------------------------------------------------- This table provides comprehensive metadata for all smart contracts deployed on EVM blockchains. It includes contract names, symbols, decimals, and deployment details read directly from the blockchain. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts#key-use-cases) Key Use Cases -------------------------------------------------------------------------------------------------------------- * Identifying contracts by name, symbol, or address * Understanding token properties (decimals, symbols) * Tracking contract deployment patterns and trends * Finding contracts deployed by specific factories or deployers * Filtering protocol-specific data across other tables [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts#important-relationships) Important Relationships ---------------------------------------------------------------------------------------------------------------------------------- * **Join with fact\_transactions**: Use `address = to_address` for contract interactions * **Join with fact\_event\_logs**: Use `address = contract_address` for contract events * **Join with ez\_token\_transfers**: Use `address = contract_address` for token movements [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts#commonly-used-fields) Commonly-used Fields ---------------------------------------------------------------------------------------------------------------------------- * `address`: The deployed contract’s blockchain address (lowercase) * `name`: Human-readable contract name from the name() function * `symbol`: Token/contract symbol from the symbol() function * `decimals`: Number of decimal places for token amounts * `creator_address`: Address that deployed this contract * `created_block_timestamp`: When the contract was created [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts#sample-queries) Sample queries ---------------------------------------------------------------------------------------------------------------- **Find All Uniswap V3 Pool Contracts** Copy Ask AI SELECT address, name, created_block_number, created_block_timestamp, creator_address FROM .core.dim_contracts WHERE creator_address = LOWER('0x1F98431c8aD98523631AE4a59f267346ea31F984') -- Uniswap V3 Factory ORDER BY created_block_number DESC LIMIT 100; **Analyze Contract Deployment Trends** Copy Ask AI SELECT DATE_TRUNC('week', created_block_timestamp) AS week, COUNT(*) AS contracts_deployed, COUNT(DISTINCT creator_address) AS unique_deployers FROM .core.dim_contracts WHERE created_block_timestamp >= CURRENT_DATE - 90 GROUP BY 1, 2 ORDER BY 1 DESC, 3 DESC; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts#columns) Columns -------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | ADDRESS | TEXT | Unique identifier - the deployed contract’s blockchain address. | Example: ‘0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48’ | | SYMBOL | TEXT | Token/contract symbol from the symbol() function. Example: ‘USDC’ | | NAME | TEXT | Human-readable contract name from the name() function. Example: ‘USD Coin’ | | DECIMALS | NUMBER | Number of decimal places for token amounts, read directly from the contract code. Example: 6 | | CREATED\_BLOCK\_NUMBER | NUMBER | Block number when contract was created. Example: 17500000 | | CREATED\_BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | Timestamp when contract was created. Example: 2023-06-15 14:30:00.000 | | CREATED\_TX\_HASH | TEXT | Transaction hash of the contract deployment. Example: ‘0x4f01db1f857e711af502ad6fa8b5b3ccd9e36b5f8c8a7b2c1d3e4f5a6b7c8d9e’ | | CREATOR\_ADDRESS | TEXT | Address that deployed this contract (transaction from\_address). Example: ‘0x95ba4cf87d6723ad9c0db21737d862be80e93911’ | | DIM\_CONTRACTS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Dim Contract Abis](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis) [Dim Labels](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels) ⌘I --- # Dim Labels - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Dim Labels [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels#commonly-used-fields) * [Sample Queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels#columns) **Schema**: `polygon.core` **Table**: `dim_labels` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels#what) What ----------------------------------------------------------------------------------------- The labels table is a critical dimension for blockchain analysis, providing one-to-one address identifiers that transform opaque addresses into recognizable entities. Labels are categorized into types (cex, dex, defi, etc.) and subtypes (hot\_wallet, treasury, etc.) to enable sophisticated filtering and analysis. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels#key-use-cases) Key Use Cases ----------------------------------------------------------------------------------------------------------- * Track centralized exchange flows (deposits, withdrawals, hot/cold wallet movements) * Analyze DeFi protocol usage and cross-protocol interactions * Monitor whale and institutional wallet activities * Identify token contracts and their movements * Assess labeling coverage for active addresses * Create entity-based transaction flow analysis [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------- * **Join with fact\_transactions**: Identify exchange flows, protocol usage * **Join with ez\_token\_transfers**: Track token movements by entity type * **Join with dim\_contracts**: Combine with contract metadata [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------- * `address`: Primary key for joining with transaction tables * `label_type`: High-level category (cex, dex, defi, token, etc.) * `label_subtype`: Specific categorization within type (hot\_wallet, pool, etc.) * `project_name`: Protocol or entity name * `address_name`: Most specific, granular label * `blockchain`: Network identifier for multi-chain queries [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels#sample-queries) Sample Queries ------------------------------------------------------------------------------------------------------------- **Exchange Flow Analysis** Copy Ask AI -- Track CEX inflows and outflows WITH cex_addresses AS ( SELECT DISTINCT address FROM .core.dim_labels WHERE label_type = 'cex' AND label_subtype IN ('hot_wallet', 'deposit') ) SELECT DATE_TRUNC('day', t.block_timestamp) AS day, CASE WHEN t.to_address IN (SELECT address FROM cex_addresses) THEN 'CEX Inflow' WHEN t.from_address IN (SELECT address FROM cex_addresses) THEN 'CEX Outflow' END AS flow_direction, COUNT(*) AS transaction_count, SUM(t.value) AS total_native_value, COUNT(DISTINCT t.from_address) AS unique_users FROM .fact.fact_transactions t WHERE (t.to_address IN (SELECT address FROM cex_addresses) OR t.from_address IN (SELECT address FROM cex_addresses)) AND t.block_timestamp >= CURRENT_DATE - 30 AND t.value > 0 GROUP BY 1, 2 ORDER BY 1 DESC, 2; **Protocol Usage Ranking** Copy Ask AI -- Top DeFi protocols by unique users SELECT l.project_name, l.label_type, COUNT(DISTINCT t.from_address) AS unique_users, COUNT(*) AS total_interactions, SUM(t.tx_fee) AS total_fees_paid FROM .fact.fact_transactions t JOIN .core.dim_labels l ON t.to_address = l.address WHERE l.label_type IN ('defi', 'dex') AND t.block_timestamp >= CURRENT_DATE - 7 AND t.tx_status = 'SUCCESS' GROUP BY 1, 2 ORDER BY 3 DESC LIMIT 20; **Whale Wallet Tracking** Copy Ask AI -- Monitor large holder activities WITH whale_activity AS ( SELECT l.address, l.address_name, l.label_type, COUNT(*) AS tx_count, SUM(CASE WHEN t.from_address = l.address THEN 1 ELSE 0 END) AS outgoing_tx, SUM(CASE WHEN t.to_address = l.address THEN 1 ELSE 0 END) AS incoming_tx, SUM(CASE WHEN t.from_address = l.address THEN t.value ELSE 0 END) AS value_sent, SUM(CASE WHEN t.to_address = l.address THEN t.value ELSE 0 END) AS value_received FROM .core.dim_labels l JOIN .fact.fact_transactions t ON l.address IN (t.from_address, t.to_address) WHERE l.label_type IN ('whale', 'institution', 'fund') AND t.block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2, 3 ) SELECT *, value_received - value_sent AS net_flow FROM whale_activity WHERE tx_count > 10 ORDER BY ABS(net_flow) DESC; **Cross-Protocol Interactions** Copy Ask AI -- Find addresses interacting with multiple protocols WITH user_protocols AS ( SELECT t.from_address AS user_address, l.project_name, l.label_type, COUNT(*) AS interactions FROM .fact.fact_transactions t JOIN .core.dim_labels l ON t.to_address = l.address WHERE l.label_type IN ('defi', 'dex', 'nft') AND t.block_timestamp >= CURRENT_DATE - 30 GROUP BY 1, 2, 3 ) SELECT user_address, COUNT(DISTINCT project_name) AS protocols_used, SUM(interactions) AS total_interactions, ARRAY_AGG(DISTINCT project_name) AS protocol_list FROM user_protocols GROUP BY 1 HAVING COUNT(DISTINCT project_name) >= 5 ORDER BY 2 DESC LIMIT 100; **Label Coverage Analysis** Copy Ask AI -- Assess labeling coverage for active addresses WITH active_addresses AS ( SELECT DISTINCT address, address_count FROM ( SELECT to_address AS address, COUNT(*) AS address_count FROM .fact.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 7 GROUP BY 1 HAVING COUNT(*) > 100 ) ) SELECT CASE WHEN l.address IS NOT NULL THEN 'Labeled' ELSE 'Unlabeled' END AS status, COUNT(*) AS address_count, SUM(a.address_count) AS total_transactions FROM active_addresses a LEFT JOIN .core.dim_labels l ON a.address = l.address GROUP BY 1; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels#columns) Columns ----------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCKCHAIN | TEXT | The blockchain network for this label. Required for multi-chain label queries. | Example: ‘ethereum’ | | CREATOR | TEXT | The source or creator of this label entry. Labels from verified sources may be more reliable. Example: ‘flipside’ | | ADDRESS | TEXT | The blockchain address (0x format) that this label describes. Lowercase hex string used as primary key for joining. Example: ‘0x1234567890123456789012345678901234567890’ | | ADDRESS\_NAME | TEXT | The most specific, granular label for this address. Provides maximum detail for precise identification. Example: ‘Binance 14’ | | LABEL\_TYPE | TEXT | High-level category describing the address’s primary function. Core types include cex, dex, defi, token, nft, bridge, games, whale, institution, and l2. Example: ‘cex’ | | LABEL\_SUBTYPE | TEXT | Specific categorization within the label type. Used for detailed filtering within broader categories. Example: ‘hot\_wallet’ | | LABEL | TEXT | High-level label identifying the general entity or wallet type. Often combines project\_name with label\_subtype. Example: ‘Binance Hot Wallet’ | | DIM\_LABELS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Dim Contracts](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts) [Ez Decoded Event Logs](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs) ⌘I --- # Ez Decoded Event Logs - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Ez Decoded Event Logs [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs#columns) **Schema**: `polygon.core` **Table**: `ez_decoded_event_logs` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs#what) What ---------------------------------------------------------------------------------------------------- This table provides human-readable decoded event data for smart contracts where ABIs are available. It transforms raw hex-encoded logs into structured JSON with named parameters and values, making blockchain data immediately queryable without manual decoding. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs#key-use-cases) Key Use Cases ---------------------------------------------------------------------------------------------------------------------- * Analyzing token transfers and approvals without manual decoding * Tracking DEX swaps and liquidity events with named parameters * Monitoring NFT transfers and marketplace activity * Querying DeFi protocol interactions (lending, staking, governance) * Building analytics on any smart contract with available ABIs [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------------ * **Join with fact\_event\_logs**: Use `tx_hash` and `event_index` for raw event data * **Join with dim\_contracts**: Use `contract_address` for contract metadata * **Join with fact\_transactions**: Use `tx_hash` for transaction context * **Cross-reference ez\_token\_transfers**: For simplified token movement data [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------------ * `contract_address`: The smart contract that emitted the event * `event_name`: The event name from the contract ABI (e.g., Transfer, Swap) * `decoded_log`: JSON object with decoded parameter names and values * `contract_name`: Human-readable name of the contract * `block_timestamp`: When the event occurred * `tx_hash`: Transaction hash containing this event [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs#sample-queries) Sample queries ------------------------------------------------------------------------------------------------------------------------ **ERC-20 Transfer Events with Proper Types** Copy Ask AI SELECT block_timestamp, tx_hash, contract_address, contract_name, event_name, decoded_log:from::string AS from_address, decoded_log:to::string AS to_address, decoded_log:value::numeric AS amount, -- Convert to decimal (assuming 18 decimals) decoded_log:value::numeric / POW(10, 18) AS amount_decimal FROM .core.ez_decoded_event_logs WHERE contract_address = LOWER('0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48') -- USDC AND event_name = 'Transfer' AND block_timestamp >= CURRENT_DATE - 7 AND decoded_log:value::numeric > 1000000000 -- Over 1000 USDC ORDER BY block_timestamp DESC; **Uniswap V3 Swap Events** Copy Ask AI SELECT block_timestamp, tx_hash, contract_address AS pool_address, event_name, decoded_log:sender::string AS sender, decoded_log:recipient::string AS recipient, decoded_log:amount0::numeric AS amount0, decoded_log:amount1::numeric AS amount1, decoded_log:sqrtPriceX96::numeric AS sqrt_price, decoded_log:liquidity::numeric AS liquidity, decoded_log:tick::integer AS tick FROM .core.ez_decoded_event_logs WHERE event_name = 'Swap' AND contract_address IN ( SELECT address FROM dim_contracts WHERE contract_name ILIKE '%Uniswap V3%' ) AND block_timestamp >= CURRENT_DATE - 1 LIMIT 100; **NFT Transfer Events (ERC-721)** Copy Ask AI SELECT block_timestamp, tx_hash, contract_address, contract_name AS collection_name, decoded_log:from::string AS from_address, decoded_log:to::string AS to_address, decoded_log:tokenId::string AS token_id FROM .core.ez_decoded_event_logs WHERE event_name = 'Transfer' AND decoded_log:tokenId IS NOT NULL -- Indicates ERC-721 AND block_timestamp >= CURRENT_DATE - 1 ORDER BY block_timestamp DESC; **DeFi Protocol Events - Compound Finance** Copy Ask AI SELECT DATE_TRUNC('day', block_timestamp) AS day, event_name, COUNT(*) AS event_count, COUNT(DISTINCT decoded_log:minter::string) AS unique_users FROM .core.ez_decoded_event_logs WHERE contract_name ILIKE '%compound%' AND event_name IN ('Mint', 'Redeem', 'Borrow', 'RepayBorrow') AND block_timestamp >= CURRENT_DATE - 30 GROUP BY 1, 2 ORDER BY 1 DESC, 3 DESC; **Complex Event Analysis - DEX Aggregator Routes** Copy Ask AI SELECT block_timestamp, tx_hash, event_name, decoded_log, ARRAY_SIZE(decoded_log:path) AS swap_hops, decoded_log:amountIn::numeric AS amount_in, decoded_log:amountOutMin::numeric AS min_amount_out FROM .core.ez_decoded_event_logs WHERE contract_address = LOWER('0x1111111254fb6c44bAC0beD2854e76F90643097d') -- 1inch AND event_name ILIKE '%swap%' AND block_timestamp >= CURRENT_DATE - 1; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs#columns) Columns ---------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | 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 | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | CONTRACT_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: - Always the immediate event emitter for logs - May differ from transaction to_address - Lowercase normalized format - Never NULL for valid events | | TOPICS | VARIANT | Array containing all indexed parameters of the event. Example: ['0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef', '0x0000000000000000000000001234567890123456789012345678901234567890'] | | TOPIC_0 | TEXT | Event signature hash - keccak256 of the event declaration. Example: '0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef' | | TOPIC_1 | TEXT | First indexed parameter of the event (if exists). Example: '0x0000000000000000000000001234567890123456789012345678901234567890' | | TOPIC_2 | TEXT | Second indexed parameter of the event (if exists). Example: '0x000000000000000000000000abcdefabcdefabcdefabcdefabcdefabcdefabcd' | | TOPIC_3 | TEXT | Third indexed parameter of the event (if exists). Example: '0x0000000000000000000000000000000000000000000000000000000000000001' | | DATA | TEXT | Hex-encoded non-indexed event parameters. Example: '0x0000000000000000000000000000000000000000000000000de0b6b3a7640000' | | EVENT_REMOVED | BOOLEAN | Boolean flag indicating if the event was removed due to chain reorganization. Example: false | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: * 0xa9059cbb: transfer(address,uint256) * 0x095ea7b3: approve(address,uint256) * 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | TX\_SUCCEEDED | BOOLEAN | Boolean indicator of transaction success. **Values**: * TRUE: Transaction executed successfully * FALSE: Transaction failed/reverted | | EVENT\_NAME | TEXT | The event name as defined in the contract’s ABI. **Format**: PascalCase event identifier **Examples**: * `Transfer` - Token transfers * `Swap` - DEX trades * `OwnershipTransferred` - Admin changes * `Approval` - Token approvals **Usage Pattern**: Copy Ask AI -- Find all event types for a contract SELECT DISTINCT event_name, COUNT(*) as occurrences FROM ez_decoded_event_logs WHERE contract_address = LOWER('0x...') GROUP BY 1 ORDER BY 2 DESC; ``` | | FULL_DECODED_LOG | VARIANT | Complete decoded event data including parameter names, values, types, and metadata. Example: '{"event_name": "Transfer", "parameters": [{"name": "from", "type": "address", "value": "0x123...", "indexed": true}]}' | | DECODED_LOG | OBJECT | Flattened JSON object containing decoded event parameters with their values. Example: '{"from": "0x123...", "to": "0x456...", "value": "1000000000000000000"}' | | CONTRACT_NAME | TEXT | Human-readable name of the smart contract emitting the event, joined from dim_contracts. Example: 'USD Coin' | | EZ_DECODED_EVENT_LOGS_ID | TEXT | Primary 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(block_number, tx_hash, 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_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Dim Labels](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels) [Ez Native Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers) ⌘I --- # Ez Native Transfers - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Ez Native Transfers [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers#columns) **Schema**: `polygon.core` **Table**: `ez_native_transfers` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers#what) 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. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers#key-use-cases) 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 [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers#important-relationships) Important Relationships ---------------------------------------------------------------------------------------------------------------------------------------- * **Join with fact\_transactions**: Use `tx_hash` for transaction context * **Join with fact\_traces**: Use `tx_hash` and `trace_index` for trace details * **Join with dim\_labels**: Use addresses for entity identification * **Complement to ez\_token\_transfers**: This table for native, that for tokens [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers#commonly-used-fields) Commonly-used Fields ---------------------------------------------------------------------------------------------------------------------------------- * `from_address`: The sender of the native asset transfer * `to_address`: The recipient of the native asset transfer * `amount`: Decimal-adjusted transfer amount * `amount_usd`: USD value at time of transfer * `origin_from_address`: Original transaction sender * `origin_to_address`: Original transaction recipient * `identifier`: Trace identifier (0 for external transfers) [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers#sample-queries) Sample queries ---------------------------------------------------------------------------------------------------------------------- **Daily Native Asset Transfer Volume** Copy Ask AI SELECT DATE_TRUNC('day', block_timestamp) AS day, COUNT(*) AS transfer_count, COUNT(DISTINCT from_address) AS unique_senders, COUNT(DISTINCT to_address) AS unique_receivers, SUM(amount) AS total_amount, AVG(amount) AS avg_amount, SUM(amount_usd) AS total_usd, MAX(amount_usd) AS largest_transfer_usd FROM .core.ez_native_transfers WHERE block_timestamp >= CURRENT_DATE - 30 AND amount > 0 GROUP BY 1 ORDER BY 1 DESC; **Whale Movements (Large Transfers)** Copy Ask AI SELECT block_timestamp, tx_hash, from_address, to_address, amount, amount_usd, origin_from_address, origin_to_address, identifier FROM .core.ez_native_transfers WHERE amount_usd > 1000000 -- Over $1M USD AND block_timestamp >= CURRENT_DATE - 7 ORDER BY amount_usd DESC LIMIT 100; **Exchange Deposit/Withdrawal Patterns** Copy Ask AI WITH exchange_addresses AS ( SELECT DISTINCT address FROM dim_labels WHERE label_type = 'exchange' ) SELECT DATE_TRUNC('hour', block_timestamp) AS hour, CASE WHEN to_address IN (SELECT address FROM exchange_addresses) THEN 'Deposit' WHEN from_address IN (SELECT address FROM exchange_addresses) THEN 'Withdrawal' END AS transfer_type, COUNT(*) AS transfer_count, SUM(amount) AS total_amount, SUM(amount_usd) AS total_usd FROM .core.ez_native_transfers WHERE block_timestamp >= CURRENT_DATE - 1 AND (to_address IN (SELECT address FROM exchange_addresses) OR from_address IN (SELECT address FROM exchange_addresses)) GROUP BY 1, 2 ORDER BY 1 DESC; **Internal Transfer Analysis** Copy Ask AI -- Compare external vs internal transfers SELECT CASE WHEN identifier = '0' THEN 'External Transfer' ELSE 'Internal Transfer' END AS transfer_type, COUNT(*) AS count, SUM(amount) AS total_amount, AVG(amount) AS avg_amount, SUM(amount_usd) AS total_volume_usd FROM .core.ez_native_transfers WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1; **Smart Contract Native Asset Holdings** Copy Ask AI WITH contract_balances AS ( SELECT to_address AS address, SUM(amount) AS inflows FROM .core.ez_native_transfers WHERE to_address IN (SELECT address FROM dim_contracts) GROUP BY 1 ), outflows AS ( SELECT from_address AS address, SUM(amount) AS outflows FROM .core.ez_native_transfers WHERE from_address IN (SELECT address FROM dim_contracts) GROUP BY 1 ) SELECT c.address, dc.name AS contract_name, COALESCE(c.inflows, 0) - COALESCE(o.outflows, 0) AS net_balance, c.inflows, o.outflows FROM contract_balances c LEFT JOIN outflows o ON c.address = o.address LEFT JOIN .core.dim_contracts dc ON c.address = dc.address WHERE COALESCE(c.inflows, 0) - COALESCE(o.outflows, 0) > 100 -- Over 100 native tokens ORDER BY net_balance DESC LIMIT 50; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers#columns) Columns -------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | 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. Example: 3 | | TRACE\_ADDRESS | TEXT | Array describing the trace’s position in the execution tree. Example: \[0, 1, 2\] | | TYPE | TEXT | The type of EVM operation performed. Example: ‘CALL’ | | FROM\_ADDRESS | TEXT | The from address for the native asset transfer. This may or may not be the same as the origin\_from\_address. Example: ‘0x1234567890123456789012345678901234567890’ | | TO\_ADDRESS | TEXT | The to address for the native asset transfer. This may or may not be the same as the origin\_to\_address. Example: ‘0xabcdefabcdefabcdefabcdefabcdefabcdefabcd’ | | AMOUNT | FLOAT | Native asset amount transferred, adjusted to standard decimal units. Example: 1.5 | | AMOUNT\_PRECISE\_RAW | TEXT | Native asset amount transferred, no decimal adjustment, returned as a string to preserve precision. Example: ‘1500000000000000000’ | | AMOUNT\_PRECISE | TEXT | Native asset amount transferred, decimal adjusted, returned as a string to preserve precision. Example: ‘1.500000000000000000’ | | AMOUNT\_USD | FLOAT | USD value of the native asset transfer at the time of the transaction. Example: 2500.50 | | ORIGIN\_FROM\_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: * 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 **Common Patterns**: * EOA → EOA: Simple transfer * EOA → Contract: User interaction * Contract → Contract: Internal calls (see fact\_traces) * Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: Copy Ask AI -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: * 0xa9059cbb: transfer(address,uint256) * 0x095ea7b3: approve(address,uint256) * 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | EZ\_NATIVE\_TRANSFERS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Decoded Event Logs](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs) [Ez Token Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers) ⌘I --- # Fact Blocks - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Blocks [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks#columns) **Schema**: `polygon.core` **Table**: `fact_blocks` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks#what) What ------------------------------------------------------------------------------------------ This table contains block-level data for EVM blockchains, providing a complete record of all blocks produced on the chain. Each row represents one block with its associated metadata, transactions, and gas metrics. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------ * Analyzing gas price trends and network congestion over time * Tracking block production rates and miner/validator performance * Monitoring network upgrades and their impact (e.g., EIP-1559, EIP-4844) * Calculating transaction throughput and network utilization * Identifying uncle blocks and chain reorganizations [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks#important-relationships) Important Relationships -------------------------------------------------------------------------------------------------------------------------------- * **Join with fact\_transactions**: Use `block_number` to analyze all transactions within a block * **Join with fact\_traces**: Use `block_number` to examine internal transactions * **Join with fact\_event\_logs**: Use `block_number` to find all events emitted in a block [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks#commonly-used-fields) Commonly-used Fields -------------------------------------------------------------------------------------------------------------------------- * `block_number`: Sequential identifier for blocks * `block_timestamp`: UTC timestamp of block production * `gas_used`: Total gas consumed by all transactions * `gas_limit`: Maximum gas allowed in the block * `base_fee_per_gas`: Base fee for EIP-1559 chains * `tx_count`: Number of transactions in the block * `miner`: Address that received block rewards [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks#sample-queries) Sample queries -------------------------------------------------------------------------------------------------------------- Copy Ask AI -- Average gas price and utilization by hour SELECT DATE_TRUNC('hour', block_timestamp) AS hour, AVG(gas_used / gas_limit) AS avg_gas_utilization, AVG(base_fee_per_gas) AS avg_base_fee, COUNT(*) AS blocks_count, SUM(tx_count) AS total_transactions FROM .core.fact_blocks WHERE block_timestamp >= CURRENT_DATE - 7 GROUP BY 1 ORDER BY 1 DESC; -- Identify high-value blocks by total gas used SELECT block_number, block_timestamp, tx_count, gas_used, gas_limit, (gas_used::FLOAT / gas_limit) AS utilization_rate, miner FROM .core.fact_blocks WHERE block_timestamp >= CURRENT_DATE - 1 ORDER BY gas_used DESC LIMIT 100; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks#columns) Columns ------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_HASH | TEXT | The unique 32-byte Keccak-256 hash of the block header, prefixed with ‘0x’. Example: ‘0x4e3a3754410177e6937ef1f84bba68ea139e8d1a2258c5f85db9f1cd715a1bdd’ | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | NETWORK | TEXT | Network identifier within the blockchain (e.g., ‘mainnet’, ‘testnet’). Example: ‘mainnet’ | | TX\_COUNT | NUMBER | Number of transactions included in the block. Example: 142 | | SIZE | NUMBER | Block size in bytes. Example: 125432 | | MINER | TEXT | Address that received block rewards. Example: ‘0xea674fdde714fd979de3edf0f56aa9716b898ec8’ | | MIX\_HASH | TEXT | 256-bit hash used in PoW mining process. Post-merge, contains prevRandao for randomness. Example: ‘0x0000000000000000000000000000000000000000000000000000000000000000’ | | EXTRA\_DATA | TEXT | Arbitrary data included by block producer (max 32 bytes). Example: ‘Geth/v1.10.23-stable/linux-amd64/go1.18.5’ | | PARENT\_HASH | TEXT | Hash of the previous block (block\_number - 1). Example: ‘0x3d7a3754410177e6937ef1f84bba68ea139e8d1a2258c5f85db9f1cd715a1bee’ | | GAS\_USED | NUMBER | Total gas consumed by all transactions in the block. Example: 15234567 | | GAS\_LIMIT | NUMBER | Maximum gas allowed for all transactions in this block. Example: 30000000 | | BASE\_FEE\_PER\_GAS | NUMBER | Base fee per gas unit in wei (EIP-1559 chains only). Example: 25000000000 | | DIFFICULTY | NUMBER | Mining difficulty at block production time. Example: 0 | | TOTAL\_DIFFICULTY | NUMBER | Cumulative difficulty from genesis to this block. Example: 58750000000000000000000 | | SHA3\_UNCLES | TEXT | Keccak-256 hash of uncle blocks list. Example: ‘0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347’ | | UNCLE\_BLOCKS | VARIANT | Array of uncle block headers (PoW only). Example: \[\] | | NONCE | NUMBER | Proof-of-Work nonce value. For PoW chains, this demonstrates computational work. Post-merge Ethereum and PoS chains typically show 0x0000000000000000. Example: ‘0x0000000000000000’ | | RECEIPTS\_ROOT | TEXT | Merkle root of all transaction receipts in the block. Example: ‘0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421’ | | STATE\_ROOT | TEXT | Merkle root of the entire blockchain state after executing this block. Example: ‘0xd7f897bbebe1f8d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d4934’ | | TRANSACTIONS\_ROOT | TEXT | Merkle root of all transactions in the block. Example: ‘0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421’ | | LOGS\_BLOOM | TEXT | 2048-bit bloom filter containing all log addresses and topics from the block’s transactions. Example: ‘0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000’ | | FACT\_BLOCKS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Token Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers) [Fact Event Logs](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs) ⌘I --- # Ez Token Transfers - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Ez Token Transfers [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers#columns) **Schema**: `polygon.core` **Table**: `ez_token_transfers` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers#what) What ------------------------------------------------------------------------------------------------- This convenience table provides a comprehensive view of all ERC-20 token transfers with enriched metadata including decimal adjustments, USD values, and token information. It simplifies token flow analysis by joining transfer events with contract details and price data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------------- * Tracking token movements and holder activity * Analyzing stablecoin flows and volumes * Monitoring DEX token inflows and outflows * Detecting new token launches and adoption * Calculating wallet token balances from transfer history [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers#important-relationships) Important Relationships --------------------------------------------------------------------------------------------------------------------------------------- * **Join with fact\_event\_logs**: Use `tx_hash` and `event_index` for raw event details * **Join with fact\_transactions**: Use `tx_hash` for transaction context * **Join with dim\_contracts**: Use `contract_address` for token metadata * **Complement to ez\_native\_transfers**: Complete picture of value flows [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers#commonly-used-fields) Commonly-used Fields --------------------------------------------------------------------------------------------------------------------------------- * `contract_address`: The token contract address (NOT the recipient) * `from_address`: Token sender address * `to_address`: Token recipient address * `amount`: Decimal-adjusted transfer amount * `amount_usd`: USD value at time of transfer * `symbol`: Token symbol (e.g., USDC, DAI) * `raw_amount`: Original amount without decimal adjustment [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers#sample-queries) Sample queries --------------------------------------------------------------------------------------------------------------------- **Top Token Transfers by USD Value** Copy Ask AI SELECT block_timestamp, tx_hash, symbol, from_address, to_address, amount, amount_usd, token_price, contract_address FROM .core.ez_token_transfers WHERE block_timestamp >= CURRENT_DATE - 7 AND amount_usd > 100000 -- Over $100k AND has_decimal = TRUE AND has_price = TRUE ORDER BY amount_usd DESC LIMIT 100; **Daily Stablecoin Volume Analysis** Copy Ask AI SELECT DATE_TRUNC('day', block_timestamp) AS day, symbol, COUNT(*) AS transfer_count, COUNT(DISTINCT from_address) AS unique_senders, SUM(amount) AS total_amount, SUM(amount_usd) AS total_usd, AVG(amount_usd) AS avg_transfer_usd FROM .core.ez_token_transfers WHERE symbol IN ('USDC', 'USDT', 'DAI', 'BUSD') AND block_timestamp >= CURRENT_DATE - 30 AND has_decimal = TRUE GROUP BY 1, 2 ORDER BY 1 DESC, 6 DESC; **DEX Token Flow Analysis** Copy Ask AI WITH dex_addresses AS ( SELECT address FROM .core.dim_labels WHERE label_type = 'dex' AND label_subtype IN ('pool', 'router') ) SELECT DATE_TRUNC('hour', block_timestamp) AS hour, symbol, CASE WHEN from_address IN (SELECT address FROM dex_addresses) THEN 'DEX Outflow' WHEN to_address IN (SELECT address FROM dex_addresses) THEN 'DEX Inflow' END AS flow_type, COUNT(*) AS transfers, SUM(amount) AS total_amount, SUM(amount_usd) AS total_usd FROM .core.ez_token_transfers WHERE block_timestamp >= CURRENT_DATE - 1 AND (from_address IN (SELECT address FROM dex_addresses) OR to_address IN (SELECT address FROM dex_addresses)) AND symbol IS NOT NULL GROUP BY 1, 2, 3 ORDER BY 1 DESC, 6 DESC; **Token Holder Activity** Copy Ask AI -- Most active token senders SELECT from_address, COUNT(DISTINCT contract_address) AS tokens_sent, COUNT(DISTINCT DATE(block_timestamp)) AS active_days, COUNT(*) AS total_transfers, SUM(amount_usd) AS total_usd_sent FROM .core.ez_token_transfers WHERE block_timestamp >= CURRENT_DATE - 30 AND has_price = TRUE AND amount_usd > 10 -- Filter dust GROUP BY 1 HAVING COUNT(*) > 10 ORDER BY total_usd_sent DESC LIMIT 100; **New Token Detection** Copy Ask AI WITH first_transfers AS ( SELECT contract_address, symbol, MIN(block_timestamp) AS first_transfer, COUNT(*) AS transfer_count, COUNT(DISTINCT from_address) AS unique_senders, COUNT(DISTINCT to_address) AS unique_receivers FROM .core.ez_token_transfers WHERE block_timestamp >= CURRENT_DATE - 7 GROUP BY 1, 2 HAVING MIN(block_timestamp) >= CURRENT_DATE - 1 ) SELECT ft.*, dc.name AS token_name, dc.decimals FROM first_transfers ft LEFT JOIN .core.dim_contracts dc ON ft.contract_address = dc.address ORDER BY transfer_count DESC; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers#columns) Columns ------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | 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 | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | FROM_ADDRESS | TEXT | The from address for the token transfer. This may or may not be the same as the origin_from_address. Example: '0x1234567890123456789012345678901234567890' | | TO_ADDRESS | TEXT | The to address for the token transfer. This may or may not be the same as the origin_to_address. Example: '0xabcdefabcdefabcdefabcdefabcdefabcdefabcd' | | CONTRACT_ADDRESS | TEXT | The contract address for the token transfer. Example: '0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48' | | TOKEN_STANDARD | TEXT | The token standard for the transfer, in this case always erc20. Example: 'erc20' | | TOKEN_IS_VERIFIED | BOOLEAN | Boolean flag indicating if the token is verified by the Flipside team. Example: true | | NAME | TEXT | Human-readable contract name from the name() function. Example: 'USD Coin' | | SYMBOL | TEXT | Token/contract symbol from the symbol() function. Example: 'USDC' | | DECIMALS | NUMBER | Number of decimal places for token amounts, read directly from the contract code. Example: 6 | | RAW_AMOUNT_PRECISE | TEXT | String representation of raw amount for precision preservation. Example: '1000500000' | | RAW_AMOUNT | FLOAT | Original token amount without decimal adjustment. Example: 1000500000 | | AMOUNT_PRECISE | TEXT | String representation of decimal-adjusted amount preserving full precision. Example: '1000.500000' | | AMOUNT | FLOAT | Decimal-adjusted token amount for human-readable values. Example: 1000.50 | | AMOUNT_USD | FLOAT | USD value of the token transfer at transaction time. Example: 1000.50 | | ORIGIN_FUNCTION_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: - 0xa9059cbb: transfer(address,uint256) - 0x095ea7b3: approve(address,uint256) - 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | EZ\_TOKEN\_TRANSFERS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Native Transfers](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers) [Fact Blocks](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks) ⌘I --- # Fact Event Logs - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Event Logs [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs#columns) **Schema**: `polygon.core` **Table**: `fact_event_logs` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs#what) What ---------------------------------------------------------------------------------------------- This table contains raw event logs emitted by smart contracts during transaction execution. Each row represents a single event with its topics and data. Events are the primary mechanism for smart contracts to communicate state changes and must be explicitly emitted in contract code. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs#key-use-cases) Key Use Cases ---------------------------------------------------------------------------------------------------------------- * Tracking raw blockchain events before decoding * Filtering events by signature (topic\_0) for specific event types * Analyzing contract activity patterns and event frequencies * Building custom event decoders for unsupported contracts * Monitoring specific addresses via indexed parameters [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------ * **Join with ez\_decoded\_event\_logs**: Use `tx_hash` and `event_index` for simplified decoded data * **Join with fact\_transactions**: Use `tx_hash` for transaction context * **Join with dim\_contracts**: Use `contract_address` for contract metadata [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------ * `topic_0`: Event signature hash for filtering event types * `contract_address`: Smart contract that emitted the event * `topics`: Array of indexed parameters (max 4) * `data`: Hex-encoded non-indexed parameters * `event_index`: Sequential position within transaction * `tx_hash`: Transaction containing this event [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs#sample-queries) Sample queries ------------------------------------------------------------------------------------------------------------------ Copy Ask AI -- Find all ERC-20 Transfer events in last 24 hours SELECT block_timestamp, tx_hash, contract_address, topics[1] AS from_address_padded, topics[2] AS to_address_padded, data AS amount_hex, event_index FROM .core.fact_event_logs WHERE topic_0 = '0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef' AND ARRAY_SIZE(topics) = 3 -- ERC-20 has 3 topics AND block_timestamp >= CURRENT_DATE - 1 LIMIT 100; -- Most active contracts by event count SELECT contract_address, COUNT(*) AS event_count, COUNT(DISTINCT tx_hash) AS unique_txs, COUNT(DISTINCT topic_0) AS unique_event_types, MIN(block_timestamp) AS first_seen, MAX(block_timestamp) AS last_seen FROM .core.fact_event_logs WHERE block_timestamp >= CURRENT_DATE - 7 GROUP BY 1 ORDER BY 2 DESC LIMIT 50; -- Event patterns within transactions SELECT tx_hash, COUNT(*) AS events_in_tx, COUNT(DISTINCT contract_address) AS contracts_touched, ARRAY_AGG(DISTINCT topic_0) AS event_signatures FROM .core.fact_event_logs WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1 HAVING COUNT(*) > 10 ORDER BY 2 DESC LIMIT 20; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs#columns) Columns ---------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | 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 | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | CONTRACT_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: - Always the immediate event emitter for logs - May differ from transaction to_address - Lowercase normalized format - Never NULL for valid events | | TOPICS | VARIANT | Array containing all indexed parameters of the event. Example: ['0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef', '0x0000000000000000000000001234567890123456789012345678901234567890'] | | TOPIC_0 | TEXT | Event signature hash - keccak256 of the event declaration. Example: '0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef' | | TOPIC_1 | TEXT | First indexed parameter of the event (if exists). Example: '0x0000000000000000000000001234567890123456789012345678901234567890' | | TOPIC_2 | TEXT | Second indexed parameter of the event (if exists). Example: '0x000000000000000000000000abcdefabcdefabcdefabcdefabcdefabcdefabcd' | | TOPIC_3 | TEXT | Third indexed parameter of the event (if exists). Example: '0x0000000000000000000000000000000000000000000000000000000000000001' | | DATA | TEXT | Hex-encoded non-indexed event parameters. Example: '0x0000000000000000000000000000000000000000000000000de0b6b3a7640000' | | EVENT_REMOVED | BOOLEAN | Boolean flag indicating if the event was removed due to chain reorganization. Example: false | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: * 0xa9059cbb: transfer(address,uint256) * 0x095ea7b3: approve(address,uint256) * 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | TX\_SUCCEEDED | BOOLEAN | Boolean indicator of transaction success. **Values**: * TRUE: Transaction executed successfully * FALSE: Transaction failed/reverted | | FACT\_EVENT\_LOGS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Fact Blocks](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks) [Fact Traces](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces) ⌘I --- # Core Tables - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Core Tables [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/overview#overview) Overview ----------------------------------------------------------------------------------------------- This schema contains 10 tables and views for Polygon data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/overview#tables-and-views) Tables and Views --------------------------------------------------------------------------------------------------------------- [Dim Contract Abis\ -----------------\ \ This table contains Application Binary Interfaces (ABIs) for smart contracts deployed on EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis) [Dim Contracts\ -------------\ \ This table provides comprehensive metadata for all smart contracts deployed on EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contracts) [Dim Labels\ ----------\ \ The labels table is a critical dimension for blockchain analysis, providing one-to-one address identifiers that transform opaque addresses into rec…](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-labels) [Ez Decoded Event Logs\ ---------------------\ \ This table provides human-readable decoded event data for smart contracts where ABIs are available.](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-decoded-event-logs) [Ez Native Transfers\ -------------------\ \ This convenience table tracks all native asset transfers (ETH, AVAX, MATIC, etc.) extracted from transaction traces.](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-native-transfers) [Ez Token Transfers\ ------------------\ \ This convenience table provides a comprehensive view of all ERC-20 token transfers with enriched metadata including decimal adjustments, USD values…](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/ez-token-transfers) [Fact Blocks\ -----------\ \ This table contains block-level data for EVM blockchains, providing a complete record of all blocks produced on the chain.](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-blocks) [Fact Event Logs\ ---------------\ \ This table contains raw event logs emitted by smart contracts during transaction execution.](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs) [Fact Traces\ -----------\ \ This table contains detailed execution traces of all internal transactions within the EVM.](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces) [Fact Transactions\ -----------------\ \ This table contains comprehensive transaction-level data for EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions) Was this page helpful? YesNo [Ez Balances Native Daily](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/balances/ez-balances-native-daily) [Dim Contract Abis](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/dim-contract-abis) ⌘I --- # Dim Dex Liquidity Pools - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Dim Dex Liquidity Pools [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools#columns) **Schema**: `polygon.defi` **Table**: `dim_dex_liquidity_pools` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools#what) What ------------------------------------------------------------------------------------------------------ This dimensional table contains comprehensive metadata for all DEX liquidity pools across supported protocols. It provides essential information about pool composition, token pairs, and configuration needed for analyzing liquidity provision and pool performance. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------------------ * Finding all pools containing specific tokens * Tracking new pool deployments * Analyzing pool configurations and fee structures * Identifying trading pairs across different protocols * Monitoring factory contract deployments [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools#important-relationships) Important Relationships -------------------------------------------------------------------------------------------------------------------------------------------- * **Join with ez\_dex\_swaps**: Use `pool_address` to get swap activity * **Join with dim\_contracts**: Use token addresses for additional metadata * **Self-join**: Find all pools with common tokens [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools#commonly-used-fields) Commonly-used Fields -------------------------------------------------------------------------------------------------------------------------------------- * `pool_address`: Unique identifier for the liquidity pool * `platform`: DEX protocol (uniswap\_v3, curve, etc.) * `pool_name`: Human-readable pool identifier * `tokens`: JSON with token0 and token1 addresses * `symbols`: JSON with token0 and token1 symbols * `creation_time`: When pool was deployed [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools#sample-queries) Sample queries -------------------------------------------------------------------------------------------------------------------------- Copy Ask AI -- Find all pools containing USDC SELECT pool_address, pool_name, platform, creation_time, CASE WHEN tokens:token0::string = LOWER('0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48') THEN symbols:token1::string ELSE symbols:token0::string END AS paired_token FROM .defi.dim_dex_liquidity_pools WHERE LOWER('0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48') IN ( tokens:token0::string, tokens:token1::string ) ORDER BY creation_time DESC; -- Recently created liquidity pools SELECT platform, pool_address, pool_name, creation_time, creation_tx, symbols:token0::string || '/' || symbols:token1::string AS pair, factory_address FROM .defi.dim_dex_liquidity_pools WHERE creation_time >= CURRENT_DATE - 7 ORDER BY creation_time DESC LIMIT 100; -- Extract token information from JSON fields SELECT pool_address, tokens:token0::string AS token0_address, tokens:token1::string AS token1_address, symbols:token0::string AS token0_symbol, symbols:token1::string AS token1_symbol, decimals:token0::integer AS token0_decimals, decimals:token1::integer AS token1_decimals FROM .defi.dim_dex_liquidity_pools WHERE platform = 'uniswap_v3'; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools#columns) Columns ------------------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | CREATION\_BLOCK | NUMBER | The block number when the liquidity pool was first created. | Example: 12369739 | | CREATION\_TIME | TIMESTAMP\_NTZ | The timestamp when the liquidity pool was deployed. Example: ‘2021-05-05 12:34:56.000’ | | CREATION\_TX | TEXT | The transaction hash that deployed this liquidity pool. Example: ‘0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef’ | | PLATFORM | TEXT | The DEX protocol where the swap occurred. Example: ‘uniswap\_v3’ | | PROTOCOL | TEXT | | | PROTOCOL\_VERSION | TEXT | | | FACTORY\_ADDRESS | TEXT | The factory contract that deployed this liquidity pool. Example: ‘0x1f98431c8ad98523631ae4a59f267346ea31f984’ | | POOL\_ADDRESS | TEXT | The liquidity pool contract address where the swap executed. Example: ‘0x8ad599c3a0ff1de082011efddc58f1908eb6e6d8’ | | POOL\_NAME | TEXT | Human-readable name for the liquidity pool. Example: ‘WETH/USDC 0.05%’ | | TOKENS | OBJECT | JSON object containing token contract addresses in the pool. Example: `{"token0": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2", "token1": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"}` | | SYMBOLS | OBJECT | JSON object containing token symbols for the pool pair. Example: `{"token0": "WETH", "token1": "USDC"}` | | DECIMALS | OBJECT | JSON object containing decimal places for each token in the pool. Example: `{"token0": 18, "token1": 6}` | | DIM\_DEX\_LIQUIDITY\_POOLS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Defi](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/overview) [Ez Bridge Activity](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity) ⌘I --- # Fact Traces - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Traces [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces#columns) **Schema**: `polygon.core` **Table**: `fact_traces` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces#what) What ------------------------------------------------------------------------------------------ This table contains detailed execution traces of all internal transactions within the EVM. While fact\_transactions shows external calls, this table reveals the complete execution flow including contract-to-contract calls, value transfers, and computation paths. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------ * Analyzing internal contract-to-contract calls and value transfers * Debugging failed transactions and understanding revert reasons * Tracking contract deployments (CREATE/CREATE2 operations) * Understanding DeFi protocol interactions and MEV analysis * Monitoring delegatecall patterns and proxy contract usage [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces#important-relationships) Important Relationships -------------------------------------------------------------------------------------------------------------------------------- * **Join with fact\_transactions**: Use `tx_hash` for transaction context * **Self-join for trace tree**: Use `tx_hash` and `trace_address` array relationships * **Join with fact\_event\_logs**: Match execution flow with events * **Join with dim\_contracts**: Get metadata for interacting contracts [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces#commonly-used-fields) Commonly-used Fields -------------------------------------------------------------------------------------------------------------------------- * `trace_index`: Sequential execution order within transaction * `trace_address`: Array showing position in execution tree * `type`: Operation type (CALL, DELEGATECALL, CREATE, etc.) * `from_address`: Address initiating this internal call * `to_address`: Destination address (NULL for contract creation) * `value`: Native token amount transferred * `trace_succeeded`: Whether execution completed successfully [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces#sample-queries) Sample queries -------------------------------------------------------------------------------------------------------------- Copy Ask AI -- Analyze internal ETH transfers SELECT block_timestamp, tx_hash, trace_index, type, from_address, to_address, value, gas_used, trace_succeeded FROM .core.fact_traces WHERE value > 0 AND type = 'CALL' AND trace_succeeded AND block_timestamp >= CURRENT_DATE - 1 ORDER BY value DESC LIMIT 100; -- Find failed internal transactions with reasons SELECT tx_hash, trace_index, from_address, to_address, type, error_reason, revert_reason, gas, gas_used FROM .core.fact_traces WHERE NOT trace_succeeded AND block_timestamp >= CURRENT_DATE - 1 AND error_reason IS NOT NULL LIMIT 50; -- Trace execution depth analysis SELECT tx_hash, MAX(ARRAY_SIZE(trace_address)) AS max_depth, COUNT(*) AS total_traces, SUM(CASE WHEN trace_succeeded THEN 0 ELSE 1 END) AS failed_traces, SUM(value) AS total_value_transferred FROM .core.fact_traces WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1 HAVING MAX(ARRAY_SIZE(trace_address)) > 3 ORDER BY 2 DESC; -- Contract interaction patterns WITH contract_calls AS ( SELECT from_address AS caller, to_address AS callee, COUNT(*) AS call_count, SUM(value) AS total_value FROM .core.fact_traces WHERE type IN ('CALL', 'DELEGATECALL') AND block_timestamp >= CURRENT_DATE - 7 GROUP BY 1, 2 ) SELECT * FROM contract_calls WHERE call_count > 100 ORDER BY call_count DESC; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces#columns) Columns ------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | 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. Example: 3 | | FROM\_ADDRESS | TEXT | Address that initiated this specific internal call. Example: ‘0x7a250d5630b4cf539739df2c5dacb4c659f2488d’ | | TO\_ADDRESS | TEXT | Destination address for this internal call. Example: ‘0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48’ | | INPUT | TEXT | Hex-encoded input data for this trace (function call data). Example: ‘0xa9059cbb0000000000000000000000001234567890123456789012345678901234567890’ | | OUTPUT | TEXT | Hex-encoded output data from trace execution. Example: ‘0x0000000000000000000000000000000000000000000000000000000000000001’ | | TYPE | TEXT | The type of EVM operation performed. Example: ‘CALL’ | | TRACE\_ADDRESS | TEXT | Array describing the trace’s position in the execution tree. Example: \[0, 1, 2\] | | SUB\_TRACES | NUMBER | Count of immediate child traces spawned by this trace. Example: 2 | | VALUE | FLOAT | Amount of native tokens transferred, in token units (not Wei). **Key Points**: * 0 for most contract interactions * > 0 for native token transfers or payable functions * Already converted from Wei (divided by 1e18) * Use value\_precise for exact amounts **Example Query**: Copy Ask AI -- Daily native token transfer volume SELECT DATE_TRUNC('day', block_timestamp) AS day, SUM(value) AS total_transferred, COUNT(*) AS transfer_count FROM .core.fact_transactions WHERE value > 0 AND tx_succeeded GROUP BY 1; ``` | | VALUE_PRECISE_RAW | TEXT | String representation of numeric values preserving exact precision without any adjustments. **Format**: VARCHAR containing numeric string **Purpose**: Prevents floating-point precision loss due to snowflake limitations **Contains**: Raw blockchain values (usually in smallest unit) **Example Values**: - "1000000000000000000" = 1 ETH in Wei - "50000000" = 50 USDC (6 decimals) **Usage**: ```sql -- Exact value comparisons WHERE value_precise_raw = '1000000000000000000' -- Conversion with precision CAST(value_precise_raw AS NUMERIC(38,0)) / POW(10, 18) AS value_decimal ``` | | VALUE_PRECISE | TEXT | String representation of numeric values adjusted for human readability while maintaining precision. **Format**: VARCHAR containing decimal string **Adjustments**: Converted from smallest unit to standard unit **Purpose**: Human-readable values without precision loss **Example Values**: - "1.0" = 1 ETH (converted from Wei) - "50.0" = 50 USDC (converted from 6 decimal places) **Best Practices**: ```sql -- Safe numeric operations CAST(value_precise AS NUMERIC(38,18)) -- Filtering large values WHERE CAST(value_precise AS NUMERIC(38,18)) > 1000 -- Aggregations SUM(CAST(value_precise AS NUMERIC(38,18))) AS total_value ``` | | VALUE_HEX | TEXT | Hexadecimal representation of transaction values as provided by the blockchain RPC. **Format**: 0x-prefixed hex string **Example**: "0xde0b6b3a7640000" = 1 ETH in Wei **Use Cases**: - Debugging RPC responses - Verifying data transformations - Handling special encoding cases **Conversion Example**: - Hex to decimal (conceptual - use built-in conversions) - 0xde0b6b3a7640000 = 1000000000000000000 Wei = 1 ETH **Note**: Most queries should use value or value_precise fields instead. | | GAS | NUMBER | Gas allocated to this specific trace execution. Example: 250000 | | GAS_USED | NUMBER | Actual gas consumed by this trace execution. Example: 125673 | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: * 0xa9059cbb: transfer(address,uint256) * 0x095ea7b3: approve(address,uint256) * 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | TRACE\_SUCCEEDED | BOOLEAN | Boolean indicating if the trace executed successfully. Example: true | | ERROR\_REASON | TEXT | Technical reason for trace failure. Example: ‘Out of gas’ | | REVERT\_REASON | TEXT | Human-readable revert message from contract require/revert statements. Example: ‘Insufficient balance’ | | TX\_SUCCEEDED | BOOLEAN | Boolean indicator of transaction success. **Values**: * TRUE: Transaction executed successfully * FALSE: Transaction failed/reverted | | FACT\_TRACES\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Fact Event Logs](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-event-logs) [Fact Transactions](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions) ⌘I --- # Fact Transactions - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Core Fact Transactions [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions#columns) **Schema**: `polygon.core` **Table**: `fact_transactions` **Type**: Base Table [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions#what) What ------------------------------------------------------------------------------------------------ This table contains comprehensive transaction-level data for EVM blockchains. Each row represents a single transaction with its execution details, gas consumption, and value transfers. This is a high-level table for analyzing on-chain activity, user behavior, and protocol interactions. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------------ * Tracking wallet activity and transaction patterns * Analyzing gas fee trends and optimization opportunities * Monitoring smart contract interactions and usage * Calculating transaction volumes and network revenue * Detecting MEV, arbitrage, and trading patterns [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions#important-relationships) Important Relationships -------------------------------------------------------------------------------------------------------------------------------------- * **Join with fact\_blocks**: Use `block_number` for block-level context * **Join with fact\_traces**: Use `tx_hash` for internal transactions * **Join with fact\_event\_logs**: Use `tx_hash` for emitted events * **Join with ez\_decoded\_event\_logs**: Use `tx_hash` for human-readable events * **Join with dim\_contracts**: Use `to_address` for contract metadata [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions#commonly-used-fields) Commonly-used Fields -------------------------------------------------------------------------------------------------------------------------------- * `tx_hash`: Unique transaction identifier * `from_address`: Transaction sender * `to_address`: Transaction recipient * `value`: Native token amount transferred * `gas_used`: Actual gas consumed * `gas_price`: Price per gas unit * `tx_fee`: Total transaction fee in native tokens * `block_timestamp`: When transaction was included [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions#sample-queries) Sample queries -------------------------------------------------------------------------------------------------------------------- Copy Ask AI -- Daily transaction statistics by type SELECT DATE_TRUNC('day', block_timestamp) AS day, tx_type, COUNT(*) AS tx_count, COUNT(DISTINCT from_address) AS unique_senders, SUM(tx_fee) AS total_fees_native, AVG(gas_used) AS avg_gas_used, PERCENTILE_CONT(0.5) WITHIN GROUP (ORDER BY gas_price) AS median_gas_price FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1, 2 ORDER BY 1 DESC, 3 DESC; -- High-value native token transfers SELECT tx_hash, block_timestamp, from_address, to_address, value, tx_fee, gas_used * gas_price / 1e9 AS gas_cost_gwei FROM .core.fact_transactions WHERE value > 0 AND tx_succeeded AND block_timestamp >= CURRENT_DATE - 7 ORDER BY value DESC LIMIT 100; -- Smart contract interaction patterns SELECT to_address, origin_function_signature, COUNT(*) AS interaction_count, COUNT(DISTINCT from_address) AS unique_users, SUM(tx_fee) AS total_fees_paid FROM .core.fact_transactions WHERE to_address IN (SELECT address FROM dim_contracts) AND block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2 ORDER BY 3 DESC LIMIT 50; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-transactions#columns) Columns ------------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | FROM\_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: * 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 **Common Patterns**: * EOA → EOA: Simple transfer * EOA → Contract: User interaction * Contract → Contract: Internal calls (see fact\_traces) * Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: Copy Ask AI -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: * 0xa9059cbb: transfer(address,uint256) * 0x095ea7b3: approve(address,uint256) * 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | VALUE | FLOAT | Amount of native tokens transferred, in token units (not Wei). **Key Points**: * 0 for most contract interactions * > 0 for native token transfers or payable functions * Already converted from Wei (divided by 1e18) * Use value\_precise for exact amounts **Example Query**: Copy Ask AI -- Daily native token transfer volume SELECT DATE_TRUNC('day', block_timestamp) AS day, SUM(value) AS total_transferred, COUNT(*) AS transfer_count FROM .core.fact_transactions WHERE value > 0 AND tx_succeeded GROUP BY 1; ``` | | VALUE_PRECISE_RAW | TEXT | String representation of numeric values preserving exact precision without any adjustments. **Format**: VARCHAR containing numeric string **Purpose**: Prevents floating-point precision loss due to snowflake limitations **Contains**: Raw blockchain values (usually in smallest unit) **Example Values**: - "1000000000000000000" = 1 ETH in Wei - "50000000" = 50 USDC (6 decimals) **Usage**: ```sql -- Exact value comparisons WHERE value_precise_raw = '1000000000000000000' -- Conversion with precision CAST(value_precise_raw AS NUMERIC(38,0)) / POW(10, 18) AS value_decimal ``` | | VALUE_PRECISE | TEXT | String representation of numeric values adjusted for human readability while maintaining precision. **Format**: VARCHAR containing decimal string **Adjustments**: Converted from smallest unit to standard unit **Purpose**: Human-readable values without precision loss **Example Values**: - "1.0" = 1 ETH (converted from Wei) - "50.0" = 50 USDC (converted from 6 decimal places) **Best Practices**: ```sql -- Safe numeric operations CAST(value_precise AS NUMERIC(38,18)) -- Filtering large values WHERE CAST(value_precise AS NUMERIC(38,18)) > 1000 -- Aggregations SUM(CAST(value_precise AS NUMERIC(38,18))) AS total_value ``` | | TX_FEE | FLOAT | Total fee paid for transaction execution in native token units. Example: 0.002 | | TX_FEE_PRECISE | TEXT | Exact transaction fee as string to prevent floating-point precision loss. Example: '0.002345678901234567' | | TX_SUCCEEDED | BOOLEAN | Boolean indicator of transaction success. **Values**: - TRUE: Transaction executed successfully - FALSE: Transaction failed/reverted | | TX_TYPE | NUMBER | Transaction envelope type (EIP-2718). Example: 2 | | NONCE | NUMBER | Sequential counter of transactions sent by the from_address. Example: 42 | | 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 | | INPUT_DATA | TEXT | Encoded data sent with the transaction, containing function calls and parameters. Example: '0xa9059cbb0000000000000000000000001234567890123456789012345678901234567890' | | GAS_PRICE | FLOAT | Price per gas unit in Gwei (1 Gwei = 1e-9 native token). Example: 25 | | EFFECTIVE_GAS_PRICE | FLOAT | Actual price paid per gas unit for EIP-1559 transactions, in Gwei. Example: 23.5 | | GAS_USED | NUMBER | Actual gas units consumed by transaction execution. Example: 89234 | | GAS_LIMIT | NUMBER | Maximum gas units the sender is willing to consume for this transaction. Example: 150000 | | CUMULATIVE_GAS_USED | NUMBER | Running total of gas consumed by all transactions up to and including this transaction within the block. Example: 1234567 | | MAX_FEE_PER_GAS | FLOAT | Maximum total fee per gas unit sender is willing to pay (EIP-1559), in Gwei. Example: 50 | | MAX_PRIORITY_FEE_PER_GAS | FLOAT | Maximum tip per gas unit for validator (EIP-1559), in Gwei. Example: 2 | | Y_PARITY | NUMBER | Y coordinate parity for signature recovery (EIP-2098). Example: 1 | | ACCESS_LIST | VARIANT | Array of addresses and storage keys for optimized gas costs (EIP-2930). Example: [{"address": "0x123...", "storageKeys": ["0x456..."]}] | | R | TEXT | R component of ECDSA signature (32 bytes). Example: '0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef' | | S | TEXT | S component of ECDSA signature (32 bytes). Example: '0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890' | | V | NUMBER | Recovery identifier for ECDSA signature. Example: 27 | | FACT_TRANSACTIONS_ID | TEXT | Primary 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(block_number, tx_hash, 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_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Fact Traces](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/core/fact-traces) [Defi](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/overview) ⌘I --- # Ez Lending Ohlc Rates - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-ohlc-rates#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Ez Lending Ohlc Rates [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-ohlc-rates#columns) **Schema**: `polygon.defi` **Table**: `ez_lending_ohlc_rates` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-ohlc-rates#columns) Columns ---------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | DAY | TIMESTAMP\_NTZ | | | PROTOCOL | TEXT | | | PLATFORM | TEXT | | | VERSION | TEXT | | | TOKEN\_ADDRESS | TEXT | | | TOKEN\_SYMBOL | TEXT | | | SUPPLY\_RATE\_OPEN | FLOAT | | | SUPPLY\_RATE\_HIGH | FLOAT | | | SUPPLY\_RATE\_LOW | FLOAT | | | SUPPLY\_RATE\_CLOSE | FLOAT | | | STABLE\_BORROW\_RATE\_OPEN | FLOAT | | | STABLE\_BORROW\_RATE\_HIGH | FLOAT | | | STABLE\_BORROW\_RATE\_LOW | FLOAT | | | STABLE\_BORROW\_RATE\_CLOSE | FLOAT | | | VARIABLE\_BORROW\_RATE\_OPEN | FLOAT | | | VARIABLE\_BORROW\_RATE\_HIGH | FLOAT | | | VARIABLE\_BORROW\_RATE\_LOW | FLOAT | | | VARIABLE\_BORROW\_RATE\_CLOSE | FLOAT | | | RATE\_UPDATES\_COUNT | NUMBER | | | BLOCKCHAIN | TEXT | | | EZ\_OHLC\_RATES\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | | | MODIFIED\_TIMESTAMP | TIMESTAMP\_NTZ | | Was this page helpful? YesNo [Ez Lending Liquidations](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations) [Ez Lending Repayments](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-repayments) ⌘I --- # Ez Bridge Activity - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Ez Bridge Activity [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity#columns) **Schema**: `polygon.defi` **Table**: `ez_bridge_activity` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity#what) What ------------------------------------------------------------------------------------------------- This table provides a comprehensive view of cross-chain bridge activity across EVM-compatible blockchains. It consolidates bridge-related events from multiple sources (event\_logs, traces, and transfers) to create a unified dataset for analyzing cross-chain asset movements. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------------- * Tracking cross-chain asset flows and bridge volumes * Analyzing user bridging behavior and patterns * Comparing bridge protocol market share and performance * Monitoring token distribution across multiple chains * Identifying popular bridge routes and corridors [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity#important-relationships) Important Relationships --------------------------------------------------------------------------------------------------------------------------------------- * **Join with core.fact\_event\_logs**: Use `tx_hash` for raw event details * **Join with core.dim\_contracts**: Use `bridge_address` or `token_address` for contract metadata * **Join with price.ez\_prices\_hourly**: For additional price validation * **Join with core.dim\_labels**: Use sender addresses for entity identification [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity#commonly-used-fields) Commonly-used Fields --------------------------------------------------------------------------------------------------------------------------------- * `platform`: Bridge protocol name * `sender`: Address sending tokens to bridge * `destination_chain`: Target blockchain for assets * `token_address`: Token being bridged * `amount`: Decimal-adjusted token amount * `amount_usd`: USD value at transaction time * `block_timestamp`: When bridge transaction occurred [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity#sample-queries) Sample queries --------------------------------------------------------------------------------------------------------------------- Copy Ask AI -- Daily bridge volume by protocol SELECT DATE_TRUNC('day', block_timestamp) AS date, platform, COUNT(DISTINCT tx_hash) AS bridge_txns, SUM(amount_usd) AS volume_usd FROM .defi.ez_bridge_activity WHERE block_timestamp >= CURRENT_DATE - 30 AND amount_usd IS NOT NULL GROUP BY 1, 2 ORDER BY 1 DESC, 3 DESC; -- Top bridge routes (source to destination chains) SELECT blockchain AS source_chain, destination_chain, platform, COUNT(*) AS transfer_count, SUM(amount_usd) AS total_volume_usd FROM .defi.ez_bridge_activity WHERE block_timestamp >= CURRENT_DATE - 7 AND destination_chain IS NOT NULL GROUP BY 1, 2, 3 ORDER BY 5 DESC LIMIT 20; -- User bridge activity analysis SELECT sender, COUNT(DISTINCT DATE_TRUNC('day', block_timestamp)) AS active_days, COUNT(DISTINCT platform) AS protocols_used, COUNT(DISTINCT destination_chain) AS chains_bridged_to, SUM(amount_usd) AS total_bridged_usd FROM .defi.ez_bridge_activity WHERE block_timestamp >= CURRENT_DATE - 30 AND amount_usd > 100 -- Filter small transfers GROUP BY 1 HAVING COUNT(*) > 5 -- Active bridgers ORDER BY 5 DESC LIMIT 100; -- Token flow analysis SELECT token_symbol, token_address, blockchain AS source_chain, destination_chain, COUNT(*) AS bridge_count, SUM(amount) AS total_amount, AVG(amount_usd) AS avg_transfer_usd FROM .defi.ez_bridge_activity WHERE block_timestamp >= CURRENT_DATE - 7 AND token_symbol IS NOT NULL GROUP BY 1, 2, 3, 4 HAVING COUNT(*) > 10 ORDER BY 5 DESC; -- Bridge protocol comparison WITH protocol_stats AS ( SELECT platform, COUNT(DISTINCT sender) AS unique_users, COUNT(*) AS total_transfers, AVG(amount_usd) AS avg_transfer_size, PERCENTILE_CONT(0.5) WITHIN GROUP (ORDER BY amount_usd) AS median_transfer_size, SUM(amount_usd) AS total_volume FROM .defi.ez_bridge_activity WHERE block_timestamp >= CURRENT_DATE - 30 AND amount_usd IS NOT NULL GROUP BY 1 ) SELECT * FROM protocol_stats ORDER BY total_volume DESC; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity#columns) Columns ------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | ORIGIN\_FROM\_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: * 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 **Common Patterns**: * EOA → EOA: Simple transfer * EOA → Contract: User interaction * Contract → Contract: Internal calls (see fact\_traces) * Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: Copy Ask AI -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: * 0xa9059cbb: transfer(address,uint256) * 0x095ea7b3: approve(address,uint256) * 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | TX\_HASH | TEXT | Unique 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` | | EVENT\_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. **Key Facts**: * Starts at 0 for first event * Increments across all contracts in transaction * Preserves execution order * Essential for deterministic event ordering **Usage Example**: Copy Ask AI -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | BRIDGE_ADDRESS | TEXT | The smart contract address handling the bridge operation. Example: '0x296f55f8fb28e498b858d0bcda06d955b2cb3f97' | | EVENT_NAME | TEXT | The event name as defined in the contract's ABI. **Format**: PascalCase event identifier **Examples**: - `Transfer` - Token transfers - `Swap` - DEX trades - `OwnershipTransferred` - Admin changes - `Approval` - Token approvals **Usage Pattern**: ```sql -- Find all event types for a contract SELECT DISTINCT event_name, COUNT(*) as occurrences FROM ez_decoded_event_logs WHERE contract_address = LOWER('0x...') GROUP BY 1 ORDER BY 2 DESC; ``` | | PLATFORM | TEXT | The protocol or application facilitating the cross-chain bridge transfer. Example: 'stargate' | | PROTOCOL | TEXT | | | PROTOCOL_VERSION | TEXT | | | SENDER | TEXT | The address that directly sent tokens to the bridge contract. Example: '0xabcdefabcdefabcdefabcdefabcdefabcdefabcd' | | RECEIVER | TEXT | The address designated to receive tokens on the destination chain (or on the source chain, for intermediate steps). Example: '0x9876543210987654321098765432109876543210' | | DESTINATION_CHAIN_RECEIVER | TEXT | The final recipient address on the destination blockchain. Example: '0xfedcbafedcbafedcbafedcbafedcbafedcbafed' | | DESTINATION_CHAIN | TEXT | The target blockchain network for the bridged assets. Example: 'arbitrum' | | DESTINATION_CHAIN_ID | TEXT | The numeric identifier for the destination blockchain. Example: 42161 | | TOKEN_ADDRESS | TEXT | The contract address of the token being bridged. Example: '0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48' | | TOKEN_SYMBOL | TEXT | The symbol identifier for the bridged token. Example: 'USDC' | | AMOUNT_UNADJ | FLOAT | The raw token amount without decimal adjustment. Example: 1000000 | | AMOUNT | FLOAT | The decimal-adjusted amount of tokens bridged. Example: 1.0 | | AMOUNT_USD | FLOAT | The hourly close USD value of bridged tokens at the time of the transaction. Example: 1000.50 | | TOKEN_IS_VERIFIED | BOOLEAN | Whether the token is verified by the Flipside team. Example: true | | EZ_BRIDGE_ACTIVITY_ID | TEXT | Primary 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(block_number, tx_hash, 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_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Dim Dex Liquidity Pools](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/dim-dex-liquidity-pools) [Ez Dex Swaps](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps) ⌘I --- # Ez Dex Swaps - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Ez Dex Swaps [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps#columns) **Schema**: `polygon.defi` **Table**: `ez_dex_swaps` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps#what) What ------------------------------------------------------------------------------------------- This table provides a comprehensive view of token swap events across major decentralized exchanges (DEXs) on EVM blockchains. It standardizes swap data from different DEX protocols into a unified format, enabling cross-DEX analysis and DeFi trading insights. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------- * Analyzing DEX trading volumes and market share * Tracking token pair liquidity and trading activity * Detecting arbitrage opportunities across protocols * Monitoring whale trades and unusual swap patterns * Calculating slippage and price impact of trades [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps#important-relationships) Important Relationships --------------------------------------------------------------------------------------------------------------------------------- * **Join with dim\_dex\_liquidity\_pools**: Get pool metadata and token details * **Join with fact\_event\_logs**: Access raw swap events * **Join with ez\_prices\_hourly**: Verify token prices [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps#commonly-used-fields) Commonly-used Fields --------------------------------------------------------------------------------------------------------------------------- * `platform`: DEX protocol (uniswap\_v2, curve, etc.) * `sender`: Address initiating the swap * `token_in`/`token_out`: Token addresses being swapped * `amount_in`/`amount_out`: Decimal-adjusted swap amounts * `amount_in_usd`/`amount_out_usd`: USD values at swap time * `pool_address`: Liquidity pool where swap occurred [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps#sample-queries) Sample queries --------------------------------------------------------------------------------------------------------------- Copy Ask AI -- Daily swap volume by DEX platform SELECT DATE_TRUNC('day', block_timestamp) AS date, platform, COUNT(*) AS swap_count, COUNT(DISTINCT sender) AS unique_traders, COUNT(DISTINCT pool_address) AS active_pools, SUM(amount_in_usd) AS total_volume_usd, AVG(amount_in_usd) AS avg_swap_size_usd, PERCENTILE_CONT(0.5) WITHIN GROUP (ORDER BY amount_in_usd) AS median_swap_usd FROM .defi.ez_dex_swaps WHERE block_timestamp >= CURRENT_DATE - 30 AND amount_in_usd IS NOT NULL AND amount_in_usd > 0 GROUP BY 1, 2 ORDER BY 1 DESC, 6 DESC; -- Most active trading pairs WITH pair_volume AS ( SELECT LEAST(token_in, token_out) AS token_a, GREATEST(token_in, token_out) AS token_b, LEAST(symbol_in, symbol_out) AS symbol_a, GREATEST(symbol_in, symbol_out) AS symbol_b, COUNT(*) AS swap_count, SUM(amount_in_usd) AS volume_usd, COUNT(DISTINCT sender) AS unique_traders, COUNT(DISTINCT DATE(block_timestamp)) AS active_days FROM .defi.ez_dex_swaps WHERE block_timestamp >= CURRENT_DATE - 7 AND amount_in_usd IS NOT NULL GROUP BY 1, 2, 3, 4 ) SELECT symbol_a || '/' || symbol_b AS pair, swap_count, volume_usd, unique_traders, active_days, volume_usd / swap_count AS avg_swap_size FROM pair_volume WHERE volume_usd > 100000 ORDER BY volume_usd DESC LIMIT 50; -- Price discrepancies across DEXs for same token pairs WITH recent_swaps AS ( SELECT block_timestamp, platform, token_in, token_out, symbol_in, symbol_out, amount_in, amount_out, amount_in_usd / NULLIF(amount_in, 0) AS price_in_usd, amount_out_usd / NULLIF(amount_out, 0) AS price_out_usd, -- Calculate implied exchange rate amount_out / NULLIF(amount_in, 0) AS exchange_rate FROM .defi.ez_dex_swaps WHERE block_timestamp >= CURRENT_TIMESTAMP - INTERVAL '1 hour' AND amount_in > 0 AND amount_out > 0 AND amount_in_usd IS NOT NULL ), price_comparison AS ( SELECT DATE_TRUNC('minute', block_timestamp) AS minute, token_in, token_out, symbol_in || '->' || symbol_out AS pair, platform, AVG(exchange_rate) AS avg_rate, COUNT(*) AS swap_count FROM recent_swaps GROUP BY 1, 2, 3, 4, 5 ) SELECT p1.minute, p1.pair, p1.platform AS platform_1, p2.platform AS platform_2, p1.avg_rate AS rate_1, p2.avg_rate AS rate_2, ABS(p1.avg_rate - p2.avg_rate) / LEAST(p1.avg_rate, p2.avg_rate) * 100 AS price_diff_pct FROM price_comparison p1 JOIN price_comparison p2 ON p1.minute = p2.minute AND p1.token_in = p2.token_in AND p1.token_out = p2.token_out AND p1.platform < p2.platform WHERE price_diff_pct > 1 -- More than 1% difference ORDER BY p1.minute DESC, price_diff_pct DESC; -- Large swaps by size and impact SELECT block_timestamp, tx_hash, platform, sender, symbol_in || ' -> ' || symbol_out AS swap_pair, amount_in, amount_in_usd, amount_out, amount_out_usd, ABS(amount_in_usd - amount_out_usd) / NULLIF(amount_in_usd, 0) * 100 AS slippage_pct FROM .defi.ez_dex_swaps WHERE block_timestamp >= CURRENT_DATE - 1 AND amount_in_usd > 100000 -- Swaps over $100k ORDER BY amount_in_usd DESC LIMIT 100; -- Platform market share by volume WITH platform_stats AS ( SELECT platform, SUM(amount_in_usd) AS total_volume, COUNT(*) AS total_swaps, COUNT(DISTINCT sender) AS unique_users, COUNT(DISTINCT pool_address) AS unique_pools FROM .defi.ez_dex_swaps WHERE block_timestamp >= CURRENT_DATE - 7 AND amount_in_usd IS NOT NULL GROUP BY 1 ) SELECT platform, total_volume, ROUND(100.0 * total_volume / SUM(total_volume) OVER (), 2) AS market_share_pct, total_swaps, unique_users, unique_pools, total_volume / NULLIF(total_swaps, 0) AS avg_swap_size FROM platform_stats ORDER BY total_volume DESC; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps#columns) Columns ------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | ORIGIN\_FUNCTION\_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: * 0xa9059cbb: transfer(address,uint256) * 0x095ea7b3: approve(address,uint256) * 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | ORIGIN\_FROM\_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: * 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 **Common Patterns**: * EOA → EOA: Simple transfer * EOA → Contract: User interaction * Contract → Contract: Internal calls (see fact\_traces) * Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: Copy Ask AI -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | CONTRACT\_ADDRESS | TEXT | The contract address of the swap. This is the address of the contract that executed the swap, often a pool contract. Example: ‘0x8ad599c3a0ff1de082011efddc58f1908eb6e6d8’ | | POOL\_NAME | TEXT | | | EVENT\_NAME | TEXT | The event name as defined in the contract’s ABI. **Format**: PascalCase event identifier **Examples**: * `Transfer` - Token transfers * `Swap` - DEX trades * `OwnershipTransferred` - Admin changes * `Approval` - Token approvals **Usage Pattern**: Copy Ask AI -- Find all event types for a contract SELECT DISTINCT event_name, COUNT(*) as occurrences FROM ez_decoded_event_logs WHERE contract_address = LOWER('0x...') GROUP BY 1 ORDER BY 2 DESC; ``` | | AMOUNT_IN_UNADJ | FLOAT | The raw, non-decimal adjusted amount of tokens provided in the swap. Example: 1000500000 | | AMOUNT_IN | FLOAT | The decimal-adjusted quantity of tokens provided by the trader in the swap. Example: 1000.5 | | AMOUNT_IN_USD | FLOAT | USD value of tokens provided in the swap at time of transaction. Example: 1500.75 | | AMOUNT_OUT_UNADJ | FLOAT | The raw, non-decimal adjusted amount of tokens received from the swap. Example: 650000000000000000 | | AMOUNT_OUT | FLOAT | The decimal-adjusted quantity of tokens received by the trader from the swap. Example: 0.65 | | AMOUNT_OUT_USD | FLOAT | USD value of tokens received from the swap at time of transaction. Example: 1498.25 | | SENDER | TEXT | The address that initiated the swap transaction. Example: '0x7a250d5630b4cf539739df2c5dacb4c659f2488d' | | TX_TO | TEXT | The recipient address of the swapped tokens. Example: '0x1234567890123456789012345678901234567890' | | EVENT_INDEX | NUMBER | Zero-based sequential position of the event within a transaction's execution. **Key Facts**: - Starts at 0 for first event - Increments across all contracts in transaction - Preserves execution order - Essential for deterministic event ordering **Usage Example**: ```sql -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | PLATFORM | TEXT | The DEX protocol where the swap occurred. Example: 'uniswap_v3' | | PROTOCOL | TEXT | The protocol used for the swap. This is the clean name of the protocol, not the platform, without the version. Example: 'uniswap' | | PROTOCOL_VERSION | TEXT | The version of the protocol used for the swap. Example: 'v3' | | TOKEN_IN | TEXT | The contract address of the token being sold in the swap. Example: '0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48' | | TOKEN_IN_IS_VERIFIED | BOOLEAN | Whether the token in the swap is verified. Example: true | | TOKEN_OUT | TEXT | The contract address of the token being received from the swap. Example: '0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2' | | TOKEN_OUT_IS_VERIFIED | BOOLEAN | Whether the token out of the swap is verified. Example: true | | SYMBOL_IN | TEXT | The ticker symbol of the token being sold/swapped from. Example: 'USDC' | | SYMBOL_OUT | TEXT | The ticker symbol of the token being bought/received. Example: 'WETH' | | _LOG_ID | TEXT | | | EZ_DEX_SWAPS_ID | TEXT | Primary 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(block_number, tx_hash, 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_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Bridge Activity](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-bridge-activity) [Ez Lending Borrows](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows) ⌘I --- # Ez Lending Flashloans - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Ez Lending Flashloans [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans#columns) **Schema**: `polygon.defi` **Table**: `ez_lending_flashloans` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans#what) What ---------------------------------------------------------------------------------------------------- This table captures flash loan transactions across lending protocols. Flash loans enable borrowing without collateral within a single transaction, provided the loan plus fees are repaid before transaction completion. This advanced DeFi primitive is primarily used for arbitrage, collateral swapping, and liquidations. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans#key-use-cases) Key Use Cases ---------------------------------------------------------------------------------------------------------------------- * Analyzing arbitrage and MEV activity patterns * Tracking flash loan volume and fee revenue * Identifying power users and bot activity * Monitoring large-scale DeFi operations * Understanding cross-protocol composability [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans#important-relationships) Important Relationships ------------------------------------------------------------------------------------------------------------------------------------------ * Often precedes transactions in DEX tables for arbitrage analysis * Links to `ez_lending_liquidations` for liquidation strategies * May connect to multiple protocols within single transaction * References `price.ez_prices_hourly` for USD valuations [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans#commonly-used-fields) Commonly-used Fields ------------------------------------------------------------------------------------------------------------------------------------ * `initiator`: Address that triggered the flash loan * `platform`: Lending protocol providing the loan * `flashloan_token`/`flashloan_token_symbol`: Borrowed asset * `flashloan_amount`/`flashloan_amount_usd`: Loan size * `premium_amount`/`premium_amount_usd`: Fee paid [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans#sample-queries) Sample queries ------------------------------------------------------------------------------------------------------------------------ Copy Ask AI -- Daily flash loan volume and fees SELECT DATE_TRUNC('day', block_timestamp) AS date, platform, COUNT(*) AS flashloan_count, SUM(flashloan_amount_usd) AS total_volume_usd, SUM(premium_amount_usd) AS total_fees_usd, AVG(premium_amount_usd / NULLIF(flashloan_amount_usd, 0) * 100) AS avg_fee_rate_pct FROM .defi.ez_lending_flashloans WHERE block_timestamp >= CURRENT_DATE - 30 AND flashloan_amount_usd IS NOT NULL GROUP BY 1, 2 ORDER BY 1 DESC, 4 DESC; -- Most flash loaned assets SELECT flashloan_token_symbol, flashloan_token, COUNT(*) AS loan_count, SUM(flashloan_amount) AS total_amount, SUM(flashloan_amount_usd) AS total_volume_usd, AVG(flashloan_amount_usd) AS avg_loan_size_usd, SUM(premium_amount_usd) AS total_fees_collected FROM .defi.ez_lending_flashloans WHERE block_timestamp >= CURRENT_DATE - 7 AND flashloan_token_symbol IS NOT NULL GROUP BY 1, 2 ORDER BY 5 DESC LIMIT 20; -- Flash loan user analysis WITH flashloan_users AS ( SELECT initiator, COUNT(*) AS flashloan_count, COUNT(DISTINCT DATE_TRUNC('day', block_timestamp)) AS active_days, COUNT(DISTINCT platform) AS protocols_used, SUM(flashloan_amount_usd) AS total_borrowed_usd, SUM(premium_amount_usd) AS total_fees_paid_usd FROM .defi.ez_lending_flashloans WHERE block_timestamp >= CURRENT_DATE - 30 AND flashloan_amount_usd IS NOT NULL GROUP BY 1 ) SELECT CASE WHEN flashloan_count = 1 THEN 'One-time User' WHEN flashloan_count <= 10 THEN 'Occasional User' WHEN flashloan_count <= 100 THEN 'Regular User' ELSE 'Power User' END AS user_category, COUNT(*) AS user_count, SUM(total_borrowed_usd) AS category_volume_usd, AVG(total_fees_paid_usd) AS avg_fees_per_user FROM flashloan_users GROUP BY 1 ORDER BY 3 DESC; -- Large flash loans (potential arbitrage/liquidations) SELECT block_timestamp, tx_hash, platform, initiator, target, flashloan_token_symbol, flashloan_amount_usd, premium_amount_usd, premium_amount_usd / NULLIF(flashloan_amount_usd, 0) * 100 AS fee_rate_pct FROM .defi.ez_lending_flashloans WHERE flashloan_amount_usd > 1000000 AND block_timestamp >= CURRENT_DATE - 1 ORDER BY flashloan_amount_usd DESC; -- Wallet-specific flash loan analysis SELECT initiator, platform, flashloan_token_symbol, COUNT(*) AS flashloan_count, SUM(flashloan_amount_usd) AS total_borrowed_usd, SUM(premium_amount_usd) AS total_fees_paid_usd, AVG(premium_amount_usd / NULLIF(flashloan_amount_usd, 0) * 100) AS avg_fee_rate_pct, MIN(block_timestamp) AS first_flashloan, MAX(block_timestamp) AS last_flashloan, COUNT(DISTINCT DATE_TRUNC('day', block_timestamp)) AS active_days FROM .defi.ez_lending_flashloans WHERE initiator = LOWER('') AND block_timestamp >= CURRENT_DATE - 30 AND flashloan_amount_usd IS NOT NULL GROUP BY 1, 2, 3 ORDER BY total_borrowed_usd DESC; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans#columns) Columns ---------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | CONTRACT\_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: * Always the immediate event emitter for logs * May differ from transaction to\_address * Lowercase normalized format * Never NULL for valid events | | EVENT\_NAME | TEXT | The event name as defined in the contract’s ABI. **Format**: PascalCase event identifier **Examples**: * `Transfer` - Token transfers * `Swap` - DEX trades * `OwnershipTransferred` - Admin changes * `Approval` - Token approvals **Usage Pattern**: Copy Ask AI -- Find all event types for a contract SELECT DISTINCT event_name, COUNT(*) as occurrences FROM ez_decoded_event_logs WHERE contract_address = LOWER('0x...') GROUP BY 1 ORDER BY 2 DESC; ``` | | EVENT_INDEX | NUMBER | Zero-based sequential position of the event within a transaction's execution. **Key Facts**: - Starts at 0 for first event - Increments across all contracts in transaction - Preserves execution order - Essential for deterministic event ordering **Usage Example**: ```sql -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | ORIGIN_FUNCTION_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: - 0xa9059cbb: transfer(address,uint256) - 0x095ea7b3: approve(address,uint256) - 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | PLATFORM | TEXT | The lending protocol where the transaction occurred. Example: ‘aave’ | | INITIATOR | TEXT | The address that triggered the flash loan execution. Example: ‘0x7a250d5630b4cf539739df2c5dacb4c659f2488d’ | | TARGET | TEXT | The contract address that receives and executes the flash loan logic. Example: ‘0x1111111254fb6c44bac0bed2854e76f90643097d’ | | PROTOCOL\_MARKET | TEXT | The lending protocol’s receipt token issued to depositors. Example: ‘0xfedcbafedcbafedcbafedcbafedcbafedcbafed’ | | TOKEN\_ADDRESS | TEXT | | | TOKEN\_SYMBOL | TEXT | | | FLASHLOAN\_TOKEN | TEXT | The contract address of the token borrowed in the flash loan. Example: ‘0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2’ This column will be deprecated October 13th, please update to token\_address. | | FLASHLOAN\_TOKEN\_SYMBOL | TEXT | The symbol of the token borrowed in the flash loan. Example: ‘WETH’ This column will be deprecated October 13th, please update to token\_symbol. | | FLASHLOAN\_AMOUNT\_UNADJ | NUMBER | The raw amount of tokens borrowed without decimal adjustment. Example: 1000000000000000000 | | FLASHLOAN\_AMOUNT | FLOAT | The decimal-adjusted amount of tokens borrowed in the flash loan. Example: 1.0 | | FLASHLOAN\_AMOUNT\_USD | FLOAT | The USD value of assets borrowed in a flash loan. Example: 1000000.50 | | PREMIUM\_AMOUNT\_UNADJ | NUMBER | The raw fee amount charged for the flash loan. Example: 900000000000000 | | PREMIUM\_AMOUNT | FLOAT | The decimal-adjusted fee paid for the flash loan. Example: 0.0009 | | PREMIUM\_AMOUNT\_USD | FLOAT | The USD value of the flash loan fee. Example: 0.90 | | EZ\_LENDING\_FLASHLOANS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Lending Deposits](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits) [Ez Lending Liquidations](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations) ⌘I --- # Ez Lending Borrows - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Ez Lending Borrows [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows#columns) **Schema**: `polygon.defi` **Table**: `ez_lending_borrows` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows#what) What ------------------------------------------------------------------------------------------------- This table provides a comprehensive view of borrowing transactions across all major lending protocols on EVM blockchains. It captures when users borrow assets against their deposited collateral, enabling analysis of lending market dynamics, user behavior, and protocol performance. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------------- * Tracking borrowing volumes and user activity across protocols * Analyzing most borrowed assets and their trends * Understanding user borrowing patterns and behavior * Monitoring protocol market share and growth * Calculating outstanding loan positions [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows#important-relationships) Important Relationships --------------------------------------------------------------------------------------------------------------------------------------- * Links to `ez_lending_deposits` for collateral analysis * Joins with `ez_lending_repayments` to track loan lifecycle * References `ez_lending_liquidations` for risk analysis * Connects to `price.ez_prices_hourly` for USD valuations [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows#commonly-used-fields) Commonly-used Fields --------------------------------------------------------------------------------------------------------------------------------- * `borrower`: Address that borrowed assets * `platform`: Lending protocol name * `token_address`/`token_symbol`: Borrowed asset details * `amount`/`amount_usd`: Borrowed quantity and USD value * `block_timestamp`: When borrow occurred [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows#sample-queries) Sample queries --------------------------------------------------------------------------------------------------------------------- Copy Ask AI -- Daily borrowing volume by protocol SELECT DATE_TRUNC('day', block_timestamp) AS date, platform, COUNT(DISTINCT tx_hash) AS borrow_txns, COUNT(DISTINCT borrower) AS unique_borrowers, SUM(amount_usd) AS volume_usd FROM .defi.ez_lending_borrows WHERE block_timestamp >= CURRENT_DATE - 30 AND amount_usd IS NOT NULL GROUP BY 1, 2 ORDER BY 1 DESC, 5 DESC; -- Top borrowed assets analysis SELECT token_symbol, token_address, COUNT(*) AS borrow_count, SUM(amount) AS total_borrowed, SUM(amount_usd) AS total_borrowed_usd, AVG(amount_usd) AS avg_borrow_size_usd FROM .defi.ez_lending_borrows WHERE block_timestamp >= CURRENT_DATE - 7 AND token_symbol IS NOT NULL GROUP BY 1, 2 ORDER BY 5 DESC LIMIT 20; -- Wallet Specific Borrow Analysis SELECT b.borrower, b.token_address AS borrowed_token_address, b.token_symbol AS borrowed_token_symbol, DATE_TRUNC('week', b.block_timestamp) AS weekly_block_timestamp, SUM(b.amount) AS total_borrow_amount, SUM(b.amount_usd) AS total_borrow_usd, SUM(r.amount) AS total_repayment_amount, SUM(r.amount_usd) AS total_repayment_usd, SUM(b.amount) - SUM(r.amount) AS net_borrowed_amount, SUM(b.amount_usd) - SUM(r.amount_usd) AS net_borrowed_usd FROM .defi.ez_lending_borrows b LEFT JOIN .defi.ez_lending_repayments r ON b.borrower = r.borrower AND b.token_address = r.token_address WHERE b.borrower = LOWER('') GROUP BY 1, 2, 3, 4 -- User borrowing patterns WITH user_stats AS ( SELECT borrower, COUNT(DISTINCT DATE_TRUNC('day', block_timestamp)) AS active_days, COUNT(DISTINCT platform) AS platforms_used, COUNT(DISTINCT token_address) AS assets_borrowed, SUM(amount_usd) AS total_borrowed_usd, AVG(amount_usd) AS avg_borrow_size FROM .defi.ez_lending_borrows WHERE block_timestamp >= CURRENT_DATE - 30 AND amount_usd IS NOT NULL GROUP BY 1 ) SELECT CASE WHEN total_borrowed_usd < 1000 THEN '< $1K' WHEN total_borrowed_usd < 10000 THEN '$1K - $10K' WHEN total_borrowed_usd < 100000 THEN '$10K - $100K' ELSE '> $100K' END AS borrower_tier, COUNT(*) AS user_count, AVG(active_days) AS avg_active_days, AVG(platforms_used) AS avg_platforms, AVG(total_borrowed_usd) AS avg_total_borrowed FROM user_stats GROUP BY 1 ORDER BY 5 DESC; -- Protocol market share WITH protocol_volume AS ( SELECT platform, SUM(amount_usd) AS total_volume, COUNT(DISTINCT borrower) AS unique_users, COUNT(*) AS transaction_count FROM .defi.ez_lending_borrows WHERE block_timestamp >= CURRENT_DATE - 30 AND amount_usd IS NOT NULL GROUP BY 1 ) SELECT platform, total_volume, total_volume * 100.0 / SUM(total_volume) OVER () AS market_share_pct, unique_users, transaction_count, total_volume / transaction_count AS avg_borrow_size FROM protocol_volume ORDER BY total_volume DESC; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows#columns) Columns ------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | CONTRACT\_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: * Always the immediate event emitter for logs * May differ from transaction to\_address * Lowercase normalized format * Never NULL for valid events | | EVENT\_NAME | TEXT | The event name as defined in the contract’s ABI. **Format**: PascalCase event identifier **Examples**: * `Transfer` - Token transfers * `Swap` - DEX trades * `OwnershipTransferred` - Admin changes * `Approval` - Token approvals **Usage Pattern**: Copy Ask AI -- Find all event types for a contract SELECT DISTINCT event_name, COUNT(*) as occurrences FROM ez_decoded_event_logs WHERE contract_address = LOWER('0x...') GROUP BY 1 ORDER BY 2 DESC; ``` | | EVENT_INDEX | NUMBER | Zero-based sequential position of the event within a transaction's execution. **Key Facts**: - Starts at 0 for first event - Increments across all contracts in transaction - Preserves execution order - Essential for deterministic event ordering **Usage Example**: ```sql -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | ORIGIN_FUNCTION_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: - 0xa9059cbb: transfer(address,uint256) - 0x095ea7b3: approve(address,uint256) - 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | PLATFORM | TEXT | The lending protocol where the transaction occurred. Example: ‘aave’ | | PROTOCOL\_MARKET | TEXT | The lending protocol’s receipt token issued to depositors. Example: ‘0xfedcbafedcbafedcbafedcbafedcbafedcbafed’ | | BORROWER | TEXT | The address that initiated a borrow or repayment transaction. Example: ‘0x1234567890123456789012345678901234567890’ | | TOKEN\_ADDRESS | TEXT | The contract address of the underlying asset being lent or borrowed. Example: ‘0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48’ | | TOKEN\_SYMBOL | TEXT | The ticker symbol of the asset involved in the lending transaction. Example: ‘USDC’ | | AMOUNT\_UNADJ | NUMBER | The raw amount of tokens borrowed or repaid without decimal adjustment. Example: 1000000000 | | AMOUNT | FLOAT | The decimal-adjusted quantity of tokens in the transaction. Example: 1000.5 | | AMOUNT\_USD | FLOAT | The USD value of tokens at transaction time. Example: 1500.75 | | EZ\_LENDING\_BORROWS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Dex Swaps](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-swaps) [Ez Lending Deposits](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits) ⌘I --- # Ez Lending Deposits - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Ez Lending Deposits [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits#columns) **Schema**: `polygon.defi` **Table**: `ez_lending_deposits` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits#what) What -------------------------------------------------------------------------------------------------- This table tracks all deposit transactions across lending protocols on EVM blockchains. Deposits represent users supplying liquidity to lending pools, earning yield while enabling their assets to serve as collateral for borrowing. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits#key-use-cases) Key Use Cases -------------------------------------------------------------------------------------------------------------------- * Calculating total value locked (TVL) by protocol * Analyzing deposit and withdrawal patterns * Tracking user liquidity provision behavior * Monitoring asset distribution across protocols * Identifying whale depositor activity [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits#important-relationships) Important Relationships ---------------------------------------------------------------------------------------------------------------------------------------- * Links to `ez_lending_borrows` for collateralization analysis * Joins with `ez_lending_withdraws` to track position lifecycle * References protocol-specific token contracts (aTokens, cTokens, etc.) * Connects to `price.ez_prices_hourly` for USD valuations [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits#commonly-used-fields) Commonly-used Fields ---------------------------------------------------------------------------------------------------------------------------------- * `depositor`: Address supplying liquidity * `platform`: Lending protocol name * `token_address`/`token_symbol`: Deposited asset details * `amount`/`amount_usd`: Deposit quantity and USD value * `block_timestamp`: When deposit occurred [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits#sample-queries) Sample queries ---------------------------------------------------------------------------------------------------------------------- Copy Ask AI -- Daily deposit volume and TVL calculation WITH daily_metrics AS ( SELECT DATE_TRUNC('day', block_timestamp) AS date, platform, SUM(amount_usd) AS daily_deposits_usd, COUNT(DISTINCT depositor) AS unique_depositors FROM .defi.ez_lending_deposits WHERE block_timestamp >= CURRENT_DATE - 30 AND amount_usd IS NOT NULL GROUP BY 1, 2 ), daily_withdrawals AS ( SELECT DATE_TRUNC('day', block_timestamp) AS date, platform, SUM(amount_usd) AS daily_withdrawals_usd FROM .defi.ez_lending_withdraws WHERE block_timestamp >= CURRENT_DATE - 30 AND amount_usd IS NOT NULL GROUP BY 1, 2 ) SELECT m.date, m.platform, m.daily_deposits_usd, COALESCE(w.daily_withdrawals_usd, 0) AS daily_withdrawals_usd, m.daily_deposits_usd - COALESCE(w.daily_withdrawals_usd, 0) AS net_flow_usd, SUM(m.daily_deposits_usd - COALESCE(w.daily_withdrawals_usd, 0)) OVER (PARTITION BY m.platform ORDER BY m.date) AS cumulative_tvl_estimate FROM daily_metrics m LEFT JOIN daily_withdrawals w ON m.date = w.date AND m.platform = w.platform ORDER BY m.date DESC, m.platform; -- Wallet level deposit and withdraw analysis SELECT d.depositor, d.token_address AS collateral_token_address, d.token_symbol AS collateral_token_symbol, DATE_TRUNC('week', d.block_timestamp) AS weekly_block_timestamp, SUM(d.amount) AS total_deposit_amount, SUM(d.amount_usd) AS total_deposit_usd, SUM(w.amount) AS total_withdraw_amount, SUM(w.amount_usd) AS total_withdraw_usd, SUM(d.amount) - SUM(w.amount) AS net_collateral_amount, SUM(d.amount_usd) - SUM(w.amount_usd) AS net_collateral_usd FROM .defi.ez_lending_deposits d LEFT JOIN .defi.ez_lending_withdraws w ON d.depositor = w.depositor AND d.token_address = w.token_address WHERE d.depositor = LOWER('') GROUP BY 1, 2, 3, 4; -- Depositor behavior analysis WITH depositor_activity AS ( SELECT depositor, COUNT(DISTINCT platform) AS platforms_used, COUNT(DISTINCT token_address) AS unique_assets, SUM(amount_usd) AS total_deposited_usd, MAX(block_timestamp) AS last_deposit, MIN(block_timestamp) AS first_deposit FROM .defi.ez_lending_deposits WHERE amount_usd IS NOT NULL GROUP BY 1 ) SELECT CASE WHEN platforms_used = 1 THEN 'Single Protocol' WHEN platforms_used = 2 THEN 'Two Protocols' ELSE 'Multi-Protocol' END AS user_type, COUNT(*) AS user_count, AVG(total_deposited_usd) AS avg_deposit_size, AVG(unique_assets) AS avg_assets_deposited, AVG(DATEDIFF('day', first_deposit, last_deposit)) AS avg_active_days FROM depositor_activity GROUP BY 1 ORDER BY 2 DESC; -- Asset distribution by protocol SELECT platform, token_symbol, COUNT(*) AS deposit_transactions, SUM(amount) AS total_amount, SUM(amount_usd) AS total_usd, SUM(amount_usd) * 100.0 / SUM(SUM(amount_usd)) OVER (PARTITION BY platform) AS pct_of_protocol FROM .defi.ez_lending_deposits WHERE block_timestamp >= CURRENT_DATE - 30 AND amount_usd IS NOT NULL AND token_symbol IS NOT NULL GROUP BY 1, 2 ORDER BY 1, 6 DESC; -- Large deposits monitoring (whale activity) SELECT block_timestamp, tx_hash, platform, depositor, token_symbol, amount, amount_usd FROM .defi.ez_lending_deposits WHERE amount_usd > 1000000 AND block_timestamp >= CURRENT_DATE - 7 ORDER BY amount_usd DESC; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-deposits#columns) Columns -------------------------------------------------------------------------------------------------------- | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | CONTRACT\_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: * Always the immediate event emitter for logs * May differ from transaction to\_address * Lowercase normalized format * Never NULL for valid events | | EVENT\_NAME | TEXT | The event name as defined in the contract’s ABI. **Format**: PascalCase event identifier **Examples**: * `Transfer` - Token transfers * `Swap` - DEX trades * `OwnershipTransferred` - Admin changes * `Approval` - Token approvals **Usage Pattern**: Copy Ask AI -- Find all event types for a contract SELECT DISTINCT event_name, COUNT(*) as occurrences FROM ez_decoded_event_logs WHERE contract_address = LOWER('0x...') GROUP BY 1 ORDER BY 2 DESC; ``` | | EVENT_INDEX | NUMBER | Zero-based sequential position of the event within a transaction's execution. **Key Facts**: - Starts at 0 for first event - Increments across all contracts in transaction - Preserves execution order - Essential for deterministic event ordering **Usage Example**: ```sql -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | ORIGIN_FUNCTION_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: - 0xa9059cbb: transfer(address,uint256) - 0x095ea7b3: approve(address,uint256) - 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | PLATFORM | TEXT | The lending protocol where the transaction occurred. Example: ‘aave’ | | PROTOCOL\_MARKET | TEXT | The lending protocol’s receipt token issued to depositors. Example: ‘0xfedcbafedcbafedcbafedcbafedcbafedcbafed’ | | DEPOSITOR | TEXT | The address that supplied liquidity to the lending protocol. Example: ‘0x9876543210987654321098765432109876543210’ | | TOKEN\_ADDRESS | TEXT | The contract address of the underlying asset being lent or borrowed. Example: ‘0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48’ | | TOKEN\_SYMBOL | TEXT | The ticker symbol of the asset involved in the lending transaction. Example: ‘USDC’ | | AMOUNT\_UNADJ | NUMBER | The raw amount of tokens borrowed or repaid without decimal adjustment. Example: 1000000000 | | AMOUNT | FLOAT | The decimal-adjusted quantity of tokens in the transaction. Example: 1000.5 | | AMOUNT\_USD | FLOAT | The USD value of tokens at transaction time. Example: 1500.75 | | EZ\_LENDING\_DEPOSITS\_ID | TEXT | Primary 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(block\_number, tx\_hash, 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\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Lending Borrows](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-borrows) [Ez Lending Flashloans](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans) ⌘I --- # Ez Lending Liquidations - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation DeFi Ez Lending Liquidations [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [What](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations#what) * [Key Use Cases](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations#key-use-cases) * [Important Relationships](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations#important-relationships) * [Commonly-used Fields](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations#commonly-used-fields) * [Sample queries](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations#sample-queries) * [Columns](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations#columns) **Schema**: `polygon.defi` **Table**: `ez_lending_liquidations` **Type**: View [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations#what) What ------------------------------------------------------------------------------------------------------ This table tracks liquidation events across lending protocols, where under-collateralized positions are forcibly closed to protect protocol solvency. Liquidations occur when a borrower’s health factor drops below 1, typically due to collateral value decline or debt value increase. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations#key-use-cases) Key Use Cases ------------------------------------------------------------------------------------------------------------------------ * Monitoring protocol health and risk levels * Analyzing liquidation patterns during market volatility * Tracking liquidator profitability and competition * Understanding collateral risk profiles * Identifying frequently liquidated borrowers [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations#important-relationships) Important Relationships -------------------------------------------------------------------------------------------------------------------------------------------- * Links to `ez_lending_borrows` for original loan details * Connects to `ez_lending_deposits` for collateral information * Often preceded by entries in `ez_lending_flashloans` * References `price.ez_prices_hourly` for USD valuations [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations#commonly-used-fields) Commonly-used Fields -------------------------------------------------------------------------------------------------------------------------------------- * `borrower`: Address that was liquidated * `liquidator`: Address performing the liquidation * `platform`: Lending protocol * `collateral_token`/`debt_token`: Asset pair involved * `amount`/`amount_usd`: Collateral seized [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations#sample-queries) Sample queries -------------------------------------------------------------------------------------------------------------------------- Copy Ask AI -- Daily liquidation volume and metrics SELECT DATE_TRUNC('day', block_timestamp) AS date, platform, COUNT(*) AS liquidation_count, COUNT(DISTINCT borrower) AS unique_borrowers_liquidated, SUM(amount_usd) AS total_debt_covered_usd, SUM(amount_usd) AS total_collateral_liquidated_usd, AVG(amount_usd / NULLIF(amount_usd, 0) - 1) * 100 AS avg_liquidation_bonus_pct FROM .defi.ez_lending_liquidations WHERE block_timestamp >= CURRENT_DATE - 30 AND amount_usd IS NOT NULL GROUP BY 1, 2 ORDER BY 1 DESC, 5 DESC; -- Most liquidated asset pairs SELECT collateral_token, collateral_token_symbol, debt_token, debt_token_symbol, COUNT(*) AS liquidation_count, SUM(amount_usd) AS total_collateral_liquidated_usd, AVG(amount_usd) AS avg_liquidation_size_usd FROM .defi.ez_lending_liquidations WHERE block_timestamp >= CURRENT_DATE - 7 AND collateral_token_symbol IS NOT NULL AND debt_token_symbol IS NOT NULL GROUP BY 1, 2, 3, 4 ORDER BY 6 DESC LIMIT 20; -- Liquidator analysis WITH liquidator_stats AS ( SELECT liquidator, COUNT(*) AS liquidations_performed, SUM(amount_usd) AS total_collateral_received_usd, FROM .defi.ez_lending_liquidations WHERE block_timestamp >= CURRENT_DATE - 30 AND amount_usd IS NOT NULL GROUP BY 1 ) SELECT CASE WHEN liquidations_performed = 1 THEN 'Opportunistic' WHEN liquidations_performed <= 10 THEN 'Active' WHEN liquidations_performed <= 100 THEN 'Professional' ELSE 'Bot/High Frequency' END AS liquidator_type, COUNT(*) AS liquidator_count, SUM(total_collateral_received_usd) as total_collateral_received_usd SUM(liquidations_performed) AS total_liquidations FROM liquidator_stats GROUP BY 1 ORDER BY 3 DESC; -- Large liquidations monitoring SELECT block_timestamp, tx_hash, platform, borrower, liquidator, collateral_token_symbol, debt_token_symbol, amount_usd, FROM .defi.ez_lending_liquidations WHERE amount_usd > 10000 AND block_timestamp >= CURRENT_DATE - 14 ORDER BY amount_usd DESC; -- Borrower liquidation history WITH borrower_liquidations AS ( SELECT borrower, COUNT(*) AS times_liquidated, COUNT(DISTINCT DATE_TRUNC('day', block_timestamp)) AS liquidation_days, SUM(amount_usd) AS total_collateral_lost_usd, ARRAY_AGG(DISTINCT platform) AS platforms_liquidated_on FROM .defi.ez_lending_liquidations WHERE block_timestamp >= CURRENT_DATE - 90 AND amount_usd IS NOT NULL GROUP BY 1 ) SELECT times_liquidated, platforms_liquidated_on, COUNT(*) AS borrower_count, AVG(total_collateral_lost_usd) AS avg_loss_from_liquidation FROM borrower_liquidations GROUP BY 1, 2 ORDER BY 1, 2; [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-liquidations#columns) Columns ------------------------------------------------------------------------------------------------------------ | Column Name | Data Type | Description | | --- | --- | --- | | BLOCK\_NUMBER | NUMBER | Sequential 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**: Copy Ask AI -- Recent data WHERE block_number >= (SELECT MAX(block_number) - 1000 FROM fact_blocks) -- Historical analysis WHERE block_number BETWEEN 15000000 AND 16000000 -- Join across tables JOIN .core.fact_event_logs USING (block_number) **Important**: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. | | BLOCK\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Time-based filtering (most efficient) WHERE block_timestamp >= DATEADD('day', -7, CURRENT_TIMESTAMP) -- Hourly aggregations DATE_TRUNC('hour', block_timestamp) AS hour -- UTC date extraction DATE(block_timestamp) AS block_date **Note**: Use for time-series analysis, but be aware that block production rates vary by chain. | | TX\_HASH | TEXT | Unique 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` | | CONTRACT\_ADDRESS | TEXT | Smart contract address that emitted this event or received the transaction. **Key Points**: * Always the immediate event emitter for logs * May differ from transaction to\_address * Lowercase normalized format * Never NULL for valid events | | EVENT\_NAME | TEXT | The event name as defined in the contract’s ABI. **Format**: PascalCase event identifier **Examples**: * `Transfer` - Token transfers * `Swap` - DEX trades * `OwnershipTransferred` - Admin changes * `Approval` - Token approvals **Usage Pattern**: Copy Ask AI -- Find all event types for a contract SELECT DISTINCT event_name, COUNT(*) as occurrences FROM ez_decoded_event_logs WHERE contract_address = LOWER('0x...') GROUP BY 1 ORDER BY 2 DESC; ``` | | EVENT_INDEX | NUMBER | Zero-based sequential position of the event within a transaction's execution. **Key Facts**: - Starts at 0 for first event - Increments across all contracts in transaction - Preserves execution order - Essential for deterministic event ordering **Usage Example**: ```sql -- Trace event execution flow SELECT event_index, contract_address, topic_0, SUBSTRING(data, 1, 10) AS data_preview FROM .core.fact_event_logs WHERE tx_hash = '0xabc...' ORDER BY event_index; ``` | | ORIGIN_FUNCTION_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. **Format**: 0x + 8 hex characters **Common Signatures**: - 0xa9059cbb: transfer(address,uint256) - 0x095ea7b3: approve(address,uint256) - 0x23b872dd: transferFrom(address,address,uint256) **Note**: NULL for simple transfers or invalid calls | | ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. **Key Points**: - 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 **Common Patterns**: - EOA → EOA: Simple transfer - EOA → Contract: User interaction - Contract → Contract: Internal calls (see fact_traces) - Known addresses: Exchange hot wallets, protocol deployers **Query Examples**: ```sql -- User activity analysis SELECT from_address, COUNT(*) as tx_count FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 30 GROUP BY 1 ORDER BY 2 DESC; -- New user detection SELECT DISTINCT from_address FROM .core.fact_transactions t1 WHERE NOT EXISTS ( SELECT 1 FROM .core.fact_transactions t2 WHERE t2.from_address = t1.from_address AND t2.block_number < t1.block_number ); ``` | | ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. **Special Cases**: - NULL: Contract creation transaction - Contract address: Interacting with smart contract - EOA address: Simple transfer or receiving funds **Important Patterns**: ```sql -- Contract deployments WHERE to_address IS NULL -- Popular contracts SELECT to_address, COUNT(*) as interactions FROM .core.fact_transactions WHERE to_address IS NOT NULL GROUP BY 1 ORDER BY 2 DESC; -- Direct transfers only WHERE to_address NOT IN (SELECT address FROM dim_contracts) **Note**: For token transfers, this is the token contract, not the recipient. See ez\_token\_transfers tables for recipient. | | PLATFORM | TEXT | The lending protocol where the transaction occurred. Example: ‘aave’ | | LIQUIDATOR | TEXT | The address that performed the liquidation. Example: ‘0xabcdefabcdefabcdefabcdefabcdefabcdefabcd’ | | BORROWER | TEXT | The address that initiated a borrow or repayment transaction. Example: ‘0x1234567890123456789012345678901234567890’ | | PROTOCOL\_MARKET | TEXT | The lending protocol’s receipt token issued to depositors. Example: ‘0xfedcbafedcbafedcbafedcbafedcbafedcbafed’ | | COLLATERAL\_TOKEN | TEXT | The token contract address used as collateral in a liquidation. Example: ‘0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2’ | | COLLATERAL\_TOKEN\_SYMBOL | TEXT | The symbol of the asset used as collateral in liquidations. Example: ‘WETH’ | | LIQUIDATED\_AMOUNT\_UNADJ | FLOAT | | | LIQUIDATED\_AMOUNT | FLOAT | | | LIQUIDATED\_AMOUNT\_USD | FLOAT | | | AMOUNT\_UNADJ | FLOAT | The raw amount of tokens liquidated without decimal adjustment. This column will be deprecated October 13th, please update to liquidated\_amount\_unadj. | | AMOUNT | FLOAT | The decimal-adjusted amount of tokens liquidated. This column will be deprecated October 13th, please update to liquidated\_amount. | | AMOUNT\_USD | FLOAT | The USD value of the tokens liquidated. This column will be deprecated October 13th, please update to liquidated\_amount\_usd. | | DEBT\_TOKEN | TEXT | The token contract address that was borrowed and is being repaid in liquidation. Example: ‘0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48’ | | DEBT\_TOKEN\_SYMBOL | TEXT | The symbol of the borrowed asset being repaid in liquidation. Example: ‘USDC’ | | REPAID\_AMOUNT\_UNADJ | NUMBER | | | REPAID\_AMOUNT | FLOAT | | | REPAID\_AMOUNT\_USD | FLOAT | | | EZ\_LENDING\_LIQUIDATIONS\_ID | TEXT | | | INSERTED\_TIMESTAMP | TIMESTAMP\_NTZ | UTC 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**: Copy Ask AI -- Check data latency SELECT DATE_TRUNC('hour', block_timestamp) as block_hour, DATE_TRUNC('hour', inserted_timestamp) as insert_hour, AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes FROM .core.fact_transactions WHERE block_timestamp >= CURRENT_DATE - 1 GROUP BY 1, 2; ``` | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC 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**: ```sql -- Recently modified records SELECT * FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp AND modified_timestamp >= CURRENT_DATE - 1; -- Data quality tracking SELECT DATE(modified_timestamp) as mod_date, COUNT(*) as records_updated, COUNT(DISTINCT block_number) as blocks_affected FROM .core.fact_transactions WHERE modified_timestamp > inserted_timestamp GROUP BY 1 ORDER BY 1 DESC; ``` | Was this page helpful? YesNo [Ez Lending Flashloans](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-flashloans) [Ez Lending Ohlc Rates](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-ohlc-rates) ⌘I --- # Nft - Flipside Docs [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/nft/overview#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation NFT Nft [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) On this page * [Overview](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/nft/overview#overview) * [Tables and Views](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/nft/overview#tables-and-views) [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/nft/overview#overview) Overview ---------------------------------------------------------------------------------------------- This schema contains 2 tables and views for Polygon data. [​](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/nft/overview#tables-and-views) Tables and Views -------------------------------------------------------------------------------------------------------------- [Ez Nft Sales\ ------------\ \ This table provides a comprehensive view of NFT (Non-Fungible Token) sales across all major marketplaces and platforms on EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/nft/ez-nft-sales) [Ez Nft Transfers\ ----------------\ \ This table contains all NFT transfer events for ERC-721 and ERC-1155 tokens on EVM blockchains.](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/nft/ez-nft-transfers) Was this page helpful? YesNo [Ez Lending Withdraws](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-lending-withdraws) [Ez Nft Sales](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/nft/ez-nft-sales) ⌘I --- # Page Not Found [Skip to main content](https://docs.flipsidecrypto.xyz/blockchain-data/polygon/defi/ez-dex-liquidity-pool-actions#content-area) [Flipside Docs home page![light logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/light.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=96312f9e0bf17141c35017172143f799)![dark logo](https://mintcdn.com/flipside-3887e776/RsSND6BtTkfacwe1/logo/dark.svg?fit=max&auto=format&n=RsSND6BtTkfacwe1&q=85&s=2b4878d77d4603d09fe0bd72590ed4ac)](https://docs.flipsidecrypto.xyz/) Search... ⌘KAsk AI Search... Navigation Page Not Found [FlipsideAI](https://docs.flipsidecrypto.xyz/flipsideai) [Snowflake Data Shares](https://docs.flipsidecrypto.xyz/snowflake-data-shares/overview) [Blockchain Data](https://docs.flipsidecrypto.xyz/blockchain-data/supported-blockchains) [Changelog](https://docs.flipsidecrypto.xyz/updates) 404 Page Not Found ============== We couldn't find the page. Maybe you were looking for one of these pages below? [Dim Dex Liquidity Pools](https://docs.flipsidecrypto.xyz/blockchain-data/blast/defi/dim-dex-liquidity-pools#dim-dex-liquidity-pools) [Ez Dex Liquidity Pool Actions](https://docs.flipsidecrypto.xyz/blockchain-data/arbitrum/defi/ez-dex-liquidity-pool-actions#ez-dex-liquidity-pool-actions) ⌘I ---