Skip to main content
Schema: blast.core 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. 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:<event_param>::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: sql 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 NameData TypeDescription
BLOCK_NUMBERNUMBERAlso known as block height. The block number, which indicates the length of the blockchain, increases after the addition of each new block.
BLOCK_TIMESTAMPTIMESTAMP_NTZThe date and time at which the block was produced.
TX_HASHTEXTTransaction hash is a unique 66-character identifier that is generated when a transaction is executed. This field will not be unique in this table, as a given transaction can include multiple events.
EVENT_INDEXNUMBEREvent number within a transaction.
CONTRACT_ADDRESSTEXTThe address interacted with for a given event.
TOPICSVARIANTThe un-decoded event input topics.
TOPIC_0TEXTThe first topic of the event, which is a unique identifier for the event.
TOPIC_1TEXTThe second topic of the event, if applicable.
TOPIC_2TEXTThe third topic of the event, if applicable.
TOPIC_3TEXTThe fourth topic of the event, if applicable.
DATATEXTThe un-decoded event data.
EVENT_REMOVEDTEXTWhether the event has been removed from the transaction.
ORIGIN_FROM_ADDRESSTEXTThe from address of this transaction.
ORIGIN_TO_ADDRESSTEXTThe to address of this transaction.
ORIGIN_FUNCTION_SIGNATURETEXTThe function signature of the contract call.
TX_SUCCEEDEDBOOLEANStatus of the transaction.
EVENT_NAMETEXTThe name of the event, as defined in the contract ABI.
FULL_DECODED_LOGVARIANTThe full decoded log, including the event name, the event parameters, and the data type of the event parameters.
DECODED_LOGOBJECTThe flattened decoded log, where the keys are the names of the event parameters, and the values are the values of the event parameters.
CONTRACT_NAMETEXTThe name of the contract, if the contract has a name() function.
EZ_DECODED_EVENT_LOGS_IDTEXTThe unique identifier for each row in the table.
INSERTED_TIMESTAMPTIMESTAMP_NTZThe utc timestamp at which the row was inserted into the table.
MODIFIED_TIMESTAMPTIMESTAMP_NTZThe utc timestamp at which the row was last modified.
TX_STATUSTEXTThis column is being deprecated for standardization purposes. Please update your queries to use the tx_succeeded column instead by March 10, 2025.