You may see duplicate records in the traces table for the zkSync 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 zksync.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

Datatypes on Snowflake datashare are different in some cases, read more here.

Table Sample

Example

Querying traces for a specific transaction hash

SELECT *
FROM zksync.traces
WHERE tx_hash = 0xb30d6d67cf7d148c2257bf598c5f5cdf5912a3d05c7d3b000398d675d2fa912c