Deprecation Notice: Lens data ingestion has been discontinued as of December 2025. Only historical data is available, and no new data will be added.
You may see duplicate records in the traces table for the Lens chain. This is not a bug, but a result of trace calls appearing twice within the same transaction. These consecutive calls—an outer and an inner call—are identical except for their gas values. They share the same from, to, input, output, success, and value fields.
Table Description
The lens.traces table contains the traces of the transactions executed on the Ethereum Virtual Machine (EVM). It includes the traces of the transaction and the traces of the internal transactions. Traces are the result of the execution of the transaction and are used to debug and understand the execution of the transaction. They are also known as `internal transactions` and can be used to understand the execution of a transaction.This is the raw version of this table. If the chain is a Fully Managed chain, decoded transaction calls will be available, see
call tables section. If this is a Hosted chain, decoded call tables will not be available.
Column Descriptions
| Column | Type | Description |
|---|
block_time | timestamp | Timestamp of the block containing this trace |
block_number | bigint | Block number containing this trace |
value | uint256 | Amount of native token transferred (in wei) |
gas | bigint | Gas provided for this trace |
gas_used | bigint | Gas consumed by this trace |
block_hash | varbinary | Hash of the block containing this trace |
success | boolean | Whether this trace executed successfully |
tx_index | integer | Position of the transaction within the block |
sub_traces | bigint | Number of child traces spawned by this trace |
error | varchar | Error message if the trace failed |
tx_success | boolean | Whether the parent transaction succeeded |
tx_hash | varbinary | Hash of the parent transaction |
from | varbinary | Address that initiated this trace |
to | varbinary | Address the trace was sent to |
trace_address | array(bigint) | Path of this trace within the call tree |
type | varchar | Type of trace (call, create, suicide, reward) |
address | varbinary | Address of the contract created (for create traces) |
code | varbinary | Bytecode of the contract created |
call_type | varchar | Type of call (call, delegatecall, staticcall) |
input | varbinary | Input data for the trace |
output | varbinary | Output data from the trace |
refund_address | varbinary | Address receiving refund (for selfdestruct) |
block_date | date | Date of the block (UTC) |
Table Sample
Example
Querying traces for a specific transaction hash
SELECT *
FROM lens.traces
WHERE tx_hash = 0xb30d6d67cf7d148c2257bf598c5f5cdf5912a3d05c7d3b000398d675d2fa912c
