| description |
|---|
Our Database automatically picks up different aspects of every transaction on the Ethereum Blockchain and parses them into different tables depending on which aspect that table is focused on. |
| Column Name | datatype | Description |
|---|---|---|
| time | timestamptz | the time when the block was mined. |
| number | numeric | the length of the blockchain in blocks |
| hash | bytea | a unique identifier for that block |
| parent hash | bytea | the unique identifier for the prior block |
| gas_limit | numeric | the gas limit of the current block |
| gas_used | numeric | the gas used in this block |
| miner | bytea | the address of the miner |
| difficulty | numeric | the effort required to mine the block |
| total_difficulty | numeric | total difficulty of the chain until this block |
| nonce | bytea | the block nonce is used to demonstrate the proof of work during mining |
| size | numeric | this block's size in bytes (limited by gas limit) |
| base_fee_per_gas | numeric | this block's base fee (introduced by EIP1559) |
This Table stores all logs that get generated by smart contracts. It is sometimes useful for querying contracts that are not yet decoded or are resistant to being decoded(we need an abi key for that).
Logs are an elegant way to store tiny amounts of data on the Ethereum blockchain for a small price. Specifically, event logs are useful to let other people know something has happened without them having to query contracts individually.
For more on this topic read this article.
| Column Name | datatype | Description |
|---|---|---|
| block_hash | bytea | a unique identifier for that block |
| block_number | int8 | the length of the blockchain in blocks |
| block_time | timestamptz | the time when the block was mined |
| contract_address | bytea | The address of the contract that emitted the log |
| data | bytea | event data |
| topic1 | bytea | indexed keys of the event |
| topic2 | bytea | indexed keys of the event |
| topic3 | bytea | indexed keys of the event |
| topic4 | bytea | indexed keys of the event |
| index | numeric | the transactions index position in the block |
| tx_hash | bytea | the transaction hash of the event |
| tx_index | numeric | the index of the transaction |
| Column Name | datatype | Description |
|---|---|---|
| block_time | timestamptz | the time when the block was mined |
| nonce | numeric | the transaction nonce, unique to that wallet |
| index | numeric | the transactions index position in the block |
| success | boolean | a true/false value that shows if the transaction suceeded |
| from | bytea | address of the sender |
| to | bytea | address of the receiver. Null when its a contract creation transaction |
| value | numeric | the amount of ether sent in this transaction in wei. note that erc20 tokens do not show up here. |
| block_number | int8 | the length of the blockchain in blocks |
| block_hash | bytea | a unique identifier for that block |
| gas_limit | numeric | the gas limit in wei |
| gas_price | numeric | the gas price in wei |
| gas_used | numeric | the gas consumed by the transaction in wei |
| data | bytea | event data |
| hash | bytea | the hash of the transaction |
| type | text | the type of the transaction: Legacy, AccessList, orDynamicFee |
| access_list | jsonb | a list of EVM memory adresses the transactions intends to access. See EIP2930. Applicable if the transaction is of type AccessList or DynamicFee |
| max_fee_per_gas | numeric | the maximum fee per gas the transaction sender is willing to pay total (introduced by EIP1559) |
| max_priority_fee_per_gas | numeric | maximum fee per gas the transaction sender is willing to give to miners to incentivize them to include their transaction (introduced by EIP1559) |
| priority_fee_per_gas | numeric | the priority fee paid out to the miner for this transaction (introduced by EIP1559) |
****Take a look for yourself****
Transactions can trigger smaller atomic actions that modify the internal state of the Ethereum Virtual Machine. Information about the execution of these actions is logged and can be found stored as an EVM execution trace, or just a trace.
Read more here.
| Column Name | datatype | Description |
|---|---|---|
| block_time | timestamptz | the time when the block was mined |
| tx_success | boolean | a true/false value that shows if the transaction succeeded |
| success | boolean | a true/false value that shows if the trace action succeeded |
| block_hash | bytea | a unique identifier for that block |
| block_number | int8 | the length of the blockchain in blocks |
| tx_hash | bytea | the transaction hash of the event |
| from | bytea | address of the sender |
| to | bytea | address of the receiver. Null when its a contract creation transaction |
| value | numeric | the amount of ether sent in this transaction in wei. note that erc20 tokens do not show up here. |
| gas | numeric | |
| gas_used | numeric | the gas consumed by the transaction in wei |
| tx_index | numeric | the index of the transaction |
| trace_address | ||
| sub_traces | ||
| type | text | type of action |
| address | bytea | the contract that is called when the type is suicide or create |
| code | bytea | |
| call_type | bytea | the type of the call |
| input | bytea | |
| output | bytea | |
| refund_address | bytea |
****Take a look for yourself****
You probably won’t use these too much when doing analysis with Dune (see decoded data), but it’s always nice to have just in case.