Credit Debit

Credit Debit tables contain the amount and direction (credit/debit) of every transfer event of all assets (ETH, ERC20, ERC721 and ERC1155) across all Ethereum wallets. This table will include two rows for every event, with one row representing credit and one row representing debit. Asset-specific tables are also available for query.

Table Details

Property	Value
Table Name	`ethereum.assets.credit_debit`
Table Status	Production-Ready
Unique Key	`transaction_hash`, `unique_id`

Table Columns

Column Name	Data Type	Description
address	VARCHAR(42)	Address of the account that was credited or debited `value` amount of token
counterparty_address	VARCHAR(42)	The address of counter party of this credit or debit transfer.
token_address	VARCHAR(42)	Token address of the asset transferred. Note: Native ETH does not have a contract address, but for convention, it is labelled as: `0x0000000000000000000000000000000000000000`
token_name	VARCHAR(16777216)	Name of the asset transferred.
token_symbol	VARCHAR(16777216)	Token symbol of the asset transferred.
token_id	VARCHAR(16777216)	Identifier for non-fungible tokens (ERC-721) or semi-fungible tokens (ERC-1155). Each unique token_id within a collection represents a distinct asset.
raw_amount	FLOAT	Amount of tokens moved (unnormalized). For ERC721 and ERC1155 tokens, there are no decimals division involved.
raw_amount_str	VARCHAR(16777216)	Raw collateral amount in USDC base units (6 decimals), as a string.
amount	FLOAT	Amount of token moved, normalized.
amount_str	VARCHAR(16777216)	Normalized token amount stored as a string to preserve full precision. Equivalent to `amount` but avoids floating-point truncation for very large or very small values.
usd_amount	FLOAT	The amount of tokens moved, in $USD.
usd_exchange_rate	FLOAT	Token symbol of this token.
transaction_from_address	VARCHAR(42)	Address of the externally-owned account (EOA) that signed and submitted the transaction. This is the wallet that paid gas, which may differ from the `from_address` of an individual token transfer if a contract is routing tokens on behalf of a user.
transaction_to_address	VARCHAR(42)	Address the transaction was sent to (the top-level `to` field of the transaction). May be a router, aggregator, or bridge contract rather than the direct recipient of assets.
transaction_hash	VARCHAR(66)	Transaction hash that this transfer belongs to.
transaction_index	NUMBER(38,0)	Zero-based position of the transaction within its block. The first transaction in a block has index 0.
block_timestamp	TIMESTAMP_NTZ(9)	The timestamp of the block that the corresponding transaction of this transfer belongs to. This is also the timestamp when this transfer occurred.
block_number	NUMBER(38,0)	The block number that the corresponding transaction of this transfer belongs to.
block_hash	VARCHAR(66)	The block hash that the corresponding transaction of this transfer belongs to.
token_type	VARCHAR(16777216)	The type of asset transferred. Currently supports ETH, ERC20, ERC721 and ERC1155 tokens.
unique_id	VARCHAR(16777216)	Unique id generated to each transfer. Includes transaction hash, log index and credit and debit transaction type.
_tokens_updated_at	TIMESTAMP_NTZ(9)	Timestamp of when the token metadata was last updated.
_created_at	TIMESTAMP_NTZ(9)	Timestamp of when the entry was created in the database.
_updated_at	TIMESTAMP_NTZ(9)	Timestamp of when the entry was last updated in the database.
_changed_since_full_refresh	BOOLEAN	Indicates if the record has changed since the last full data refresh.

Difference with transfers

Unlike token transfers, data here is organized into credit and debit rows (similar to the accounting concept called “double entry book”).

Advantages Over Transfer Tables

Balance Calculation
- Easy summation of all credits and debits for an address
- Simplified queries for net position calculations
- Natural handling of complex transactions
Flow Analysis
- Clear visualization of token inflows and outflows
- Simple aggregation of total volume by address
- Easy identification of major senders/receivers
Data Consistency
- Built-in verification through balanced entries
- Self-auditing through equal total credits and debits
- Simplified reconciliation process

Sample Query

Debit and credit of ETH from a particular transaction.

select * from ethereum.assets.credit_debit
where block_number = '5030097'
and transaction_hash = '0x1c2eb8b98e9917b30e402d519c1545116e7432699dffced4041c980cd8b6a4d6'

Getting the cumulative change of USDC holdings in Uniswap v3 USDC-WETH pool in the last 30 days

select
  date(block_timestamp) as date,
  token_name, 
  sum(amount) as delta,
  sum(delta) over (order by date) as net_change
from
  ethereum.assets.credit_debit
  where address = '0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640' -- USDC-ETH Uniswap v3 5bp
  and token_address = '0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48' -- USDC Token Address
and current_date - date(block_timestamp) < 30
group by date, token_name
order by date desc 

EVM Assets Credit Debit

Overview

Data Verticals

Solana

Hyperliquid

Lighter

Bitcoin Ecosystem

EVM

Cosmos Ecosystem

Move Ecosystem

Other Ecosystems

Table Details

Table Columns

Difference with transfers

Advantages Over Transfer Tables

Sample Query

​Table Details

​Table Columns

​Difference with transfers

​Advantages Over Transfer Tables

​Sample Query

​Related Docs

Table Details

Table Columns

Difference with transfers

Advantages Over Transfer Tables

Sample Query

Related Docs