BitqueryBitqueryData Store
Tron logoTronTransfers

TRON USDT Transfers

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.

Coverage
Apr 16, 2019→ Nov 15, 2026 · yesterday
Rows
≈872Mrows · estimate
Size
≈99 GBParquet · estimate
Table
1usdt_transfers
Columns
43typed
Coverage ends yesterday, UTC

Overview

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.

Use cases

  • 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

Table

43 columns · free sample for the table

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.

tron/tron-usdt-transfers/usdt_transfers<YYYY-MM-DD>.parquetone file per UTC day, sorted by block
Browse columns Sample fileSample updated Nov 16, 2026

Schema reference

copies a column name
43 columns
ColumnTypeDescription
Block3
Block_NumberInt64Block height
Block_TimeDateTimeBlock timestamp, UTC (Parquet timestamp in milliseconds; the file stores no time zone)
Block_DateDateUTC date of the block
Transfer12
Transfer_AmountStringUSDT transferred, decimal adjusted (6 decimals), as a decimal string. Multiply by 10^6 for the raw on-chain integer
Transfer_AmountInUSDFloat64Amount valued in USD at the hourly USDT price for the block's hour, so close to but not exactly the USDT amount
Transfer_CallIndexUInt64Index of the call the transfer happened in
Transfer_TransactionIndexUInt64Position of the transaction within the block
Transfer_URIStringMetadata URI for non-fungible transfers; empty otherwise
Transfer_SuccessStringWhether the transfer succeeded; true or false
Transfer_SenderStringSending address, base58
Transfer_ReceiverStringReceiving address, base58
Transfer_LogIndexUInt64Log index within the transaction; the event index for TRC-20 transfers
Transfer_IndexUInt32Position within the transaction. Several rows in one transaction can share it
Transfer_DataStringRaw transfer payload; empty on TRX, TRC-10 and TRC-20 transfers, which is all of them today
Transfer_IdStringToken id for non-fungible transfers; the string 0 when there is none
Transfer_Currency11
Transfer_Currency_AssetIdStringTRC-10 asset id; empty for TRC-20, so empty on every row here
Transfer_Currency_DecimalsInt32Decimals of the transferred currency; 6 for USDT
Transfer_Currency_DelegatedStringWhether the currency is delegated; the string true or false
Transfer_Currency_DelegatedToStringAddress the currency is delegated to; empty when it is not
Transfer_Currency_FungibleStringWhether the currency is fungible; true or false
Transfer_Currency_NameStringName of the transferred currency, Tether USD
Transfer_Currency_HasURIStringWhether the currency carries a metadata URI; true or false
Transfer_Currency_NativeStringtrue for native TRX, false for tokens; false on every row here
Transfer_Currency_SymbolStringSymbol reported by the contract, USDT
Transfer_Currency_SmartContractStringContract of the transferred token, base58. Always TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t, Tether's USDT on TRON
Transfer_Currency_ProtocolNameStringToken standard, trc20
Witness2
Witness_SignatureStringSignature of the block producer
Witness_AddressStringAddress of the block producer
TransactionStatus1
TransactionStatus_SuccessStringWhether the transaction succeeded; the string true or false
Transaction4
Transaction_FeeStringTransaction fee in TRX, decimal adjusted from SUN, as a decimal string
Transaction_FeePayerStringAddress that paid the fee, which is the transaction sender
Transaction_HashStringHash of the transaction this transfer settled in; the join key to the transactions and events tables
Transaction_FeeInUSDFloat64Transaction fee valued in USD at the hourly TRX price for the block's hour
Log4
Log_Signature_NameStringDecoded event name, Transfer on every row
Log_Signature_SignatureStringFull event signature, Transfer(address,address,uint256) on every row
Log_Signature_TypeStringWhether the event signature came from a registered ABI; the string true or false
Log_Signature_SignatureHashStringEvent topic0, hex without a 0x prefix
Contract2
Contract_AddressStringContract the transaction called; the USDT contract for direct transfers, a router or exchange contract when the transfer happened inside another call
Contract_TypeStringTRON contract type, TriggerSmartContract for TRC-20 transfers
Call4
Call_Signature_NameStringDecoded function name, for example transfer or transferFrom
Call_Signature_SignatureStringFull function signature
Call_Signature_TypeStringWhether the function signature came from a registered ABI; the string true or false
Call_Signature_SignatureHashStringFour-byte selector, hex without a 0x prefix
Sample file

Ask an AI about this data

Send this dataset’s full schema to an assistant and ask it anything. It reads the plain-text brief first, so the answer comes from the real column list rather than a guess.

Start with

Opens a new chat with the question filled in. Nothing about you is sent to Bitquery, and the assistant sees only the public brief.

Delivery

Parquet files in a Requester Pays S3 bucket or a Cloudflare R2 bucket, chosen at checkout. On S3 you download with your own AWS account and AWS bills the transfer; on R2 you download with a read-only API key and pay no egress. Layout:

# usdt_transfers: one file per UTC day, sorted by block
tron/tron-usdt-transfers/usdt_transfers<YYYY-MM-DD>.parquet
  1. Download a free sampleNo email needed.
  2. Pay nowName, work email and licence check.
  3. Pay the invoiceBy card or bank transfer.
  4. Download from S3 or R2The team prepares the export and emails the bucket path, plus a read-only API key for R2 orders.

Need new data after your purchase?

Kafka Streams sends new Tron data in real time, so your copy can stay current after the files end. It is sold on an Enterprise plan.

Read the Kafka docs

Time windows

Every window includes 43 columns. Only the time range changes.

31 days
Latest month
Oct 15, 2026 → Nov 15, 2026
$100
Pay now
184 days
Last 6 months
May 15, 2026 → Nov 15, 2026
$300
Pay now
365 days
Last 12 months
Nov 15, 2025 → Nov 15, 2026
$600
Pay now
2,770 days
Full history
Apr 16, 2019 → Nov 15, 2026
$1,800
Pay now
In every window
  • The usdt_transfers table, 43 columns
  • Parquet files in the layout under Delivery
  • S3 or R2 download, chosen at checkout
  • Licensed under the Data License

FAQ

11 questions
What is in the TRON USDT Transfers dataset?

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.

How big is it?

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.

How does it differ from the full TRON Transfers dataset?

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.

Are Approval events or other logs mixed in?

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.

How do I get the net USDT flow of one address?

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.

What was left out, and why?

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.

How are the rows produced, and how were they checked?

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.

How is the USD value set?

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.

What should I watch out for?

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.

How do I load it?

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.

How current is it, and how is it delivered?

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.