Flipside Docs
Search…
Ethereum Transactions Table
Ethereum transactions exist within the ethereum schema, as ethereum.transactions .
Transactions contain top-level summary information not found in ethereum.udm_events, for example, transaction fees and gas.

How are transactions modeled along-side events?

Case #1: Native Eth Transfer (no contracts called)
If Person A, sent 5 ETH to PersonB, this would results in 1 record in the transactions table, and 1 event in ethereum.udm_events to record the "transfer" event.
Case #2: ERC-20 Transfer (contract call)
If Person A, sent 10 USDC to Person B, this would result in 1 record in ethereum.transactions , and 1 event in ethereum.udm_events to record the "transfer" event.
In cases where more complex contract methods are called, multiple events are recorded in the event table with a reference back to the transaction.

Table Schema

ethereum.transactions
Field
Type
Description
block_number
number
The block height this event was recorded at.
block_timestamp
timestamp
UTC block timestamp for parent block
event_count
number
The number of events contained within this transaction.
fee
number
The transaction fee calculated from the gas price and the gas used.
fee_usd
number
The USD equivalent fee at the time of the transaction.
from_address
address
The sender/initiator of the transaction.
from_addres_name
label
from_label_subtype
label
function_name
string
The English decoded name of the function signature, if applicable.
function_signature
string
The function signature of the contract call, if applicable.
gas_limit
number
The gas limit specified in this transaction.
gas_price
number
The gas price at the time of this transaction.
gas_used
number
The amount of gas used by this transaction.
nonce
number
The number of transactions sent from the from_address.
success
text
The success state of this transaction execution.
symbol
text
The project symbol (i.e. ERC-20 transaction), if applicable.
to_address
text
The recipient of the transaction, or contract being called.