A USDT TRC-20 transfer uses 65,000 energy when the receiver already holds USDT and 131,000 when it does not. Without energy the network burns 100 SUN of TRX for every missing unit, 6.50 TRX for a usual transfer, so renting the energy first is what makes transfers cheap.
Enter how many transfers you send a day: the calculator prices them at today's live rental price and shows the monthly total next to the cost of burning TRX.
Receivers
Price
30 days
4,944 TRX
19,500 TRX burning TRX instead SAVE 74 %
195,000,000 energy in 30 days
Sending this every day? A contract fixes the price — Talk to us →
Each transfer is one 1-hour order at 25.34 SUN per energy; an order total rounds up to 1,000 SUN, as quotes do. Day average = the day's windows weighted by length. Burn: 100 SUN per energy (getEnergyFee). Schedule from the published grid.
| Receiver | Energy | TRX burned |
|---|---|---|
| Already holds USDT | 65,000 | 6.50 TRX |
| Holds no USDT | 131,000 | 13.10 TRX |
100 SUN per energy (chain parameter getEnergyFee). Chain parameters as of 2026-10-01.
A transfer spends bandwidth as well as energy: about 345 points for a USDT transfer. Every activated account gets 600 free bandwidth points a day, which covers one transfer; past that the network burns TRX for bandwidth too, about 0.35 TRX a transfer.
Rental prices follow the clock: cheapest at night (UTC), highest in the afternoon. The price map on the pricing page shows every window of the day in your time zone, so batches can be scheduled into the cheap hours.
When the receiver's USDT balance is zero, the token contract writes a new balance record, which costs about as much energy again: 130,285 instead of 64,285 measured on mainnet, sold as 131,000 and 65,000. It is the balance at that moment that counts, not whether the address ever held USDT.
From our live price API, the same price an order is charged: the cheapest provider's price for the amount, with no markup.
No. It runs in your browser on the public price feed; nothing is bought until you place an order.