# TRON USDT Transfers | Bitquery Data Store Every USDT (TRC-20) transfer on TRON, one row per Transfer event, with sender, receiver, amount, fee and USD value, for the last 1 to 12 months. Dataset page: https://bitquery.io/datastore/datasets/tron-usdt-transfers Network: Tron Category: Transfers Tables: 1 Columns: 43 Coverage: 2019-04-16 to 2026-11-15 Rows: about 872M Size: about 99 GB Format: Apache Parquet, ZSTD compression, one prefix per table Licence: https://bitquery.io/datastore/legal/data-license ## What this is TRON USDT transfers are the tron-transfers dataset cut to one contract, TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t, Tether's USDT on TRON. We decode the chain ourselves and keep only Transfer(address,address,uint256) events, so Approval events never show up as transfers, which is the usual trap with explorer TRC-20 endpoints. Each row is one transfer with sender, receiver, the exact amount as a decimal string, a USD value from our hourly price series, the transaction fee in TRX and USD, and the block producer. The columns are the same 43, in the same order, as tron-transfers, so code written for one reads the other. USDT is about 29% of all TRON transfer rows: 3.81 billion of 13.25 billion since April 2019, and about 70 million a month in 2026. The query most buyers run first is net flow per address: sum Transfer_Amount received per Transfer_Receiver minus sent per Transfer_Sender, keeping Transfer_Success = 'true'. Amounts are decimal strings, so cast to a decimal type rather than a float when you sum. ## What people use it for - USDT payment flow for exchanges, merchants and payment processors on TRON - Deposit and withdrawal attribution for known wallets - USDT balance history for any address, rebuilt from its transfers - Volume, active-address and transfer-size statistics for TRC-20 USDT ## Tables (1) ### usdt_transfers: 43 columns One row per USDT (TRC-20) Transfer event on TRON, with sender, receiver, amount, USD value, fee and status. Same 43 columns as tron-transfers. Bucket prefix: tron/tron-usdt-transfers/usdt_transfers File naming: .parquet, one file per UTC day, sorted by block Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/tron/tron-usdt-transfers/usdt_transfers/sample.parquet Sample updated: Nov 16, 2026 | column | type | description | | --- | --- | --- | | Block_Number | Int64 | Block height | | Block_Time | DateTime | Block timestamp, UTC (Parquet timestamp in milliseconds; the file stores no time zone) | | Block_Date | Date | UTC date of the block | | Transfer_Amount | String | USDT transferred, decimal adjusted (6 decimals), as a decimal string. Multiply by 10^6 for the raw on-chain integer | | Transfer_AmountInUSD | Float64 | Amount valued in USD at the hourly USDT price for the block's hour, so close to but not exactly the USDT amount | | Transfer_CallIndex | UInt64 | Index of the call the transfer happened in | | Transfer_Currency_AssetId | String | TRC-10 asset id; empty for TRC-20, so empty on every row here | | Transfer_Currency_Decimals | Int32 | Decimals of the transferred currency; 6 for USDT | | Transfer_Currency_Delegated | String | Whether the currency is delegated; the string true or false | | Transfer_Currency_DelegatedTo | String | Address the currency is delegated to; empty when it is not | | Transfer_Currency_Fungible | String | Whether the currency is fungible; true or false | | Transfer_Currency_Name | String | Name of the transferred currency, Tether USD | | Transfer_Currency_HasURI | String | Whether the currency carries a metadata URI; true or false | | Transfer_Currency_Native | String | true for native TRX, false for tokens; false on every row here | | Transfer_Currency_Symbol | String | Symbol reported by the contract, USDT | | Transfer_Currency_SmartContract | String | Contract of the transferred token, base58. Always TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t, Tether's USDT on TRON | | Transfer_Currency_ProtocolName | String | Token standard, trc20 | | Transfer_TransactionIndex | UInt64 | Position of the transaction within the block | | Transfer_URI | String | Metadata URI for non-fungible transfers; empty otherwise | | Transfer_Success | String | Whether the transfer succeeded; true or false | | Transfer_Sender | String | Sending address, base58 | | Transfer_Receiver | String | Receiving address, base58 | | Transfer_LogIndex | UInt64 | Log index within the transaction; the event index for TRC-20 transfers | | Transfer_Index | UInt32 | Position within the transaction. Several rows in one transaction can share it | | Transfer_Data | String | Raw transfer payload; empty on TRX, TRC-10 and TRC-20 transfers, which is all of them today | | Transfer_Id | String | Token id for non-fungible transfers; the string 0 when there is none | | Witness_Signature | String | Signature of the block producer | | Witness_Address | String | Address of the block producer | | TransactionStatus_Success | String | Whether the transaction succeeded; the string true or false | | Transaction_Fee | String | Transaction fee in TRX, decimal adjusted from SUN, as a decimal string | | Transaction_FeePayer | String | Address that paid the fee, which is the transaction sender | | Transaction_Hash | String | Hash of the transaction this transfer settled in; the join key to the transactions and events tables | | Transaction_FeeInUSD | Float64 | Transaction fee valued in USD at the hourly TRX price for the block's hour | | Log_Signature_Name | String | Decoded event name, Transfer on every row | | Log_Signature_Signature | String | Full event signature, Transfer(address,address,uint256) on every row | | Log_Signature_Type | String | Whether the event signature came from a registered ABI; the string true or false | | Log_Signature_SignatureHash | String | Event topic0, hex without a 0x prefix | | Contract_Address | String | Contract the transaction called; the USDT contract for direct transfers, a router or exchange contract when the transfer happened inside another call | | Contract_Type | String | TRON contract type, TriggerSmartContract for TRC-20 transfers | | Call_Signature_Name | String | Decoded function name, for example transfer or transferFrom | | Call_Signature_Signature | String | Full function signature | | Call_Signature_Type | String | Whether the function signature came from a registered ABI; the string true or false | | Call_Signature_SignatureHash | String | Four-byte selector, hex without a 0x prefix | ## Price - Latest month (Oct 15, 2026 → Nov 15, 2026): $100 one-time, USD - Last 6 months (May 15, 2026 → Nov 15, 2026): $300 one-time, USD - Last 12 months (Nov 15, 2025 → Nov 15, 2026): $600 one-time, USD - Full history (Apr 16, 2019 → Nov 15, 2026): $1,800 one-time, USD Every window includes all 43 columns. Only the time range changes. ## Questions buyers ask Q: What is in the TRON USDT Transfers dataset? A: One Parquet table, usdt_transfers, with 43 columns: every transfer of USDT on TRON (contract TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t) in the window you buy, one row per Transfer event. Each row has sender, receiver, amount, USD value, the transaction hash, fee and status, and the call that moved the tokens. Q: How big is it? A: About 70 million rows a month: 70.5 million in October 2026 and 871.9 million in the 12 months from November 2025 to October 2026, counted on the live table. At about 114 bytes per row as ZSTD Parquet, measured on 11,119 rows, that is roughly 8 GB a month and 99 GB for 12 months. These are estimates until the delivery manifest gives exact figures. Q: How does it differ from the full TRON Transfers dataset? A: Same columns, same formats, same export query, with the rows cut to the USDT contract. tron-transfers also holds TRX, TRC-10 and every other TRC-20 token, about 3.5 times as many rows. If you only need USDT, this is the smaller download and the lower price. Q: Are Approval events or other logs mixed in? A: No. The export keeps only rows whose event is Transfer(address,address,uint256). On 10 November 2026 the USDT contract produced 2,497,069 transfer rows and every one carried that signature. TronGrid's TRC-20 endpoint, by contrast, returns Approval events in the same list, which inflates counts and volume if they are not filtered out. Q: How do I get the net USDT flow of one address? A: Filter Transfer_Receiver or Transfer_Sender to the address and Transfer_Success to 'true', then sum Transfer_Amount in minus out. Summing every transfer of an address from its first one gives its balance at any point in time. We build balances this way on purpose: transfers match the chain, while balance tables can miss outflows. Q: What was left out, and why? A: Every other token and native TRX, which are in tron-transfers. Failed transfers stay in, about 0.1% of rows (878 of 2,497,069 on 10 November 2026), marked by Transfer_Success and TransactionStatus_Success. Lookalike tokens named USDT are not included, because the filter is the contract address, not the symbol. Q: How are the rows produced, and how were they checked? A: Decoded from TRON mainnet by our own indexer and read from the per-contract transfers table. The export query was run on 1 November 2026: 1,980,181 rows, 1,978,775 successful, every row joined to its block and every row carrying the USDT contract. The free sample is 100 rows from block 87,821,823 onward, 8 November 2026. Q: How is the USD value set? A: Transfer_AmountInUSD is the USDT amount times our hourly USDT price for the block's hour, so it sits close to the token amount, for example $1,016.65 for 1,018 USDT at a price of 0.99867. If you want USDT counted at exactly one dollar, use Transfer_Amount instead. Q: What should I watch out for? A: Amounts are decimal strings, so casting to float loses precision on large values. A transfer made inside a contract call (an exchange router, a multisend) has Contract_Address set to that contract, not to USDT. Several rows can share one Transaction_Hash; the row key is Transaction_Hash plus Transfer_LogIndex. Q: How do I load it? A: One line in DuckDB: SELECT * FROM read_parquet('usdt_transfers/*.parquet') LIMIT 10. Pandas works too: pandas.read_parquet(path). The sample file opens without credentials. Q: How current is it, and how is it delivered? A: A purchase covers the window you choose up to yesterday, UTC. Files are Parquet, ZSTD-compressed, one per day, named by date and sorted by block, with a JSON manifest listing every file and its sha256. We prepare them within 7 business days of purchase and email you the location: a Requester Pays S3 bucket downloaded with your own AWS account, or a Cloudflare R2 bucket with a read-only key, as chosen at checkout. Files stay available for 7 days from delivery. ## Data after your purchase A purchase is a one-time set of files, up to the coverage end date on the dataset page. For data after that: - Real-time stream: Kafka Streams sends new Tron data as it happens. Enterprise plan. Topics and schema: https://docs.bitquery.io/docs/streams/kafka-streaming-concepts/#tron-tron - Daily warehouse tables: Datashares refreshes tables daily in Snowflake, BigQuery, S3 or Azure. Enterprise plan. https://bitquery.io/products/datashares - Another one-off slice (other chains, tables or dates): a custom extract. https://bitquery.io/products/data-on-demand ## What this file is, and is not This is a description of one dataset sold by Bitquery, written for assistants and for people. It lists every column but holds no data rows. The sample files linked under each table are real Parquet and are free to download. Figures here come from the product record and are exact unless marked otherwise; the delivery manifest is authoritative for a purchased file. If a question needs a row that is not in a sample, say so rather than guessing at it.