Credit Debit tables contain the amount and direction (credit/debit) of every transfer event of TRX. 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.Documentation Index
Fetch the complete documentation index at: https://docs.allium.so/llms.txt
Use this file to discover all available pages before exploring further.
Difference with transfers
Unlike token transfers, data here is organized into credit and debit rows (similar to the accounting concept called “double entry book”).Methodology
Using TRX as an example, a token transfer will be represented as follows:| from_address | to_address | amount | event |
|---|---|---|---|
| X | Y | 1250 | X transfers 1250 tokens to Y |
| address | counterparty_address | amount | event |
|---|---|---|---|
| X | Y | -1250 | X decrease 1250 tokens to Y |
| Y | X | 1250 | Y increase 1250 tokens from X |
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