Skip to main content
Schema: ethereum.ens Table: ez_ens_domains Type: View A convenience table with up-to-date details pertaining to ENS domains registered onchain. Note, records are derived directly from onchain event logs only and may not be inclusive of off-chain activity.

​
Columns

Column NameData TypeDescription
LAST_REGISTERED_BLOCKNUMBERThe latest block number in which the domain was registered.
LAST_REGISTERED_TIMESTAMPTIMESTAMP_NTZThe timestamp corresponding to the latest block in which the domain was registered.
LAST_REGISTERED_TX_HASHTEXTTransaction hash of the most recent domain registration event.
LAST_REGISTERED_CONTRACTTEXTThe contract address responsible for the most recent domain registration.
MANAGERTEXTThe address that currently manages the domain.
OWNERTEXTThe address that currently owns the domain.
SET_ADDRESSTEXTThe address that the domain currently resolves to.
ENS_SETBOOLEANIndicates if the domain has been set to an address.
ENS_DOMAINTEXTThe primary domain name.
ENS_SUBDOMAINSARRAYAny subdomains that are associated with the primary domain.
LABELTEXTThe label hash, which is a representation of the domain.
NODETEXTA hash representing the ENS domain.
TOKEN_IDTEXTThe ID of the token associated with the domain.
LAST_REGISTERED_COSTFLOATThe cost associated with the most recent registration of the domain.
LAST_REGISTERED_PREMIUMFLOATAny additional premium paid during the most recent registration of the domain.
RENEWAL_COSTFLOATThe cost to renew the domain’s registration.
EXPIRATION_TIMESTAMPTIMESTAMP_NTZThe timestamp at which the domain registration will expire.
EXPIREDBOOLEANIndicates if the domain registration has expired.
RESOLVERTEXTThe address of the resolver contract that provides records for the domain.
PROFILEOBJECTProfile information, such as avatars or social links, associated with the domain.
LAST_UPDATEDTIMESTAMP_NTZThe timestamp of the last update made to the domain’s record or last updated record in this table.
EZ_ENS_DOMAINS_IDTEXTPrimary key - unique identifier for each row ensuring data integrity.
Format: Usually VARCHAR containing composite key generated using MD5 hash of the relevant columns. Example: MD5(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: 
-- 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 <blockchain_name>.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 <blockchain_name>.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 <blockchain_name>.core.fact_transactions
WHERE modified_timestamp > inserted_timestamp
GROUP BY 1
ORDER BY 1 DESC;
``` |