Table Overview
All tables are located in thestablecoins.intelligence schema. Each table is per-transfer grain and cross-chain.
Access tiers. The full-history tables are gated (entitled customers). Each is also published as a rolling last-30-days view that is broadly shared, identical schema, filtered to
block_timestamp >= dateadd('day', -30, current_timestamp()):stablecoins.intelligence.enriched_transfers_last_30d
*_last_30d view for evaluation and rolling analytics; contact Allium for full-history access.1. enriched_transfers
Purpose: Cross-chain stablecoin transfers enriched with registry metadata, an activity taxonomy, directional flow categories, and the adjusted-volume gate. Use Case: Adjusted payment volume, organic-vs-noise analysis, flow analysis by counterparty sector.Schema
Example Queries
Total Adjusted Volume by Chain (30d)
Top Stablecoins by Organic Volume
2. organic_activity_classification
Purpose: Assigns each organic transfer a sender/receiver wallet type, balance tier, and high-level transaction intent. Use Case: Who is transacting (consumer vs business vs institutional) and why (payments vs trading vs savings).Schema
Transaction Types
Wallet Types
Example Query — Transaction Type Distribution
3. payment_categorization
Purpose: Granular payment category and purpose for transfers classified asReal-World Payment.
Use Case: Payment-use-case analytics, merchant insights, payroll/remittance tracking.
Schema
Includes the wallet-type/balance-tier context fromorganic_activity_classification, plus:
Only transfers with
transaction_type = 'Real-World Payment' are present in this table. Consumer-to-institutional (C2I) deposits are treated as Investment/Trade and excluded from the real-world payment mix. Institutional flows (I2C, I2B, B2I, I2I) are rolled into their respective B2B/B2C categories.Core Payment Categories
Payment Purposes (by flow)
Example Query — Payment Purpose Breakdown
Table Relationships
enriched_transfers is the per-transfer base (adjusted-volume gate + flow categories). organic_activity_classification adds wallet typing and intent; payment_categorization adds purpose for the real-world-payment subset. Join across them on chain + transaction_hash (+ unique_id where a transaction has multiple legs).
Next Steps
Adjusted Volume Methodology
Learn how organic volume is calculated
Pipeline Overview
Back to payments pipeline overview