Take the recipient's address from their own deposit screen: on the TRON network it starts with the letter T and is 34 characters long. In the wallet, first pick the TRON network, then paste the address, enter the amount and sign the transfer. Keep a reserve of TRX on the balance — without it the network will not let the transfer through. How much: in the measurement below the full price of a transfer is 6.43 TRX, and to an address with no USDT history 13.03 TRX; the reserve is worked out from the higher figure.
After that the network does the work. A transfer lands in a block in three seconds on average and shows its result at that same moment, and it becomes irreversible in about a minute — that is nineteen blocks. Measurement of 19.09.2026: out of 949 USDT transfers on TRON, 98.53% went through. Of the fourteen that failed, thirteen failed for one and the same reason: there was no TRX in the wallet, and the money stayed where it was. The fourteenth was a contract rejection, and there the fee was charged.
The price does not depend on the amount being sent. In the same measurement 46.6% of senders paid nothing, the median was 0.345 TRX, and only 8% burned the full price: 6.43 TRX, or 13.03 TRX to an address that had never once held USDT. When the recipient sees the money on their side is decided by them, not by the network.
What you need in hand before you press “Send”
Four things, and each one is a separate point of failure. The first two are obvious, the other two are not.
what you need | where it comes from | what happens if it is missing |
|---|---|---|
the recipient's address on the TRON network | from the recipient's deposit page | the transfer goes to another network or nowhere |
USDT on the balance | — | the contract refuses to carry out the operation |
TRX on the balance | bought separately | rejection on zero energy, the transfer does not go through |
the recipient has held USDT before | not visible in advance | the price of the transfer doubles |
An address in the TRC20 standard is exactly 34 characters long and always starts with T at the front. Where to get it in different wallets is covered separately: a wallet for USDT TRC20 and ERC20. The same piece explains why the fee is taken in TRX and not in the USDT itself.
An important caveat about these signs: “T and 34 characters” will not tell a wallet address apart from a smart-contract address — the format is the same for both. The explorer keeps them in separate sections: a wallet opens as /address/…, a contract as /contract/…/code. USDT that has gone to a contract cannot be brought back, which is why the address is only ever taken from the deposit page.
The fourth row cannot be checked in the wallet: we found no app that would warn you before sending that the recipient has never held USDT. You can only see it in the explorer: put the recipient's address into the search on Tronscan — the account page opens at /address/…/transactions — and look at the list of tokens. No USDT history means the transfer costs twice as much.
The vendor of the multi-chain wallet Keeper confirms the mechanics: on the first receipt of USDT the contract creates a new storage cell for the address, so the first top-up is always dearer than the ones after it. Their price range is “usually 7 to 15 TRX”, help page as of 19.09.2026.
The order of the steps, and why the network is picked before the address
The order below comes from a multi-chain wallet vendor's help page, which covers TRON along with the other networks. App screens differ; the sequence does not. The labels Send and Comment are given in English, as in the help page: we did not open a live app and did not check the localisation.
- Open the wallet and tap
Send. - Pick the network — TRON — and the token you are sending.
- Paste or scan the recipient's address and make sure it belongs to the same network you have just picked.
- Fill in the
Commentfield if the recipient asks for a comment — but on TRON this step does not exist: the vendor warns that the field is “available only for TON-based tokens”. When sending TRC20 the step is skipped. - Enter the amount, look at the fee, confirm and sign the transfer.
First thing to notice: the network is picked at step two, before the address. Pasting an address into a form set to the wrong network is the most expensive mistake in this whole subject, and it happens precisely when the network is switched last.
Second: when you send TRC20 there is no memo field at all. Not “you may leave it blank” — it is physically not shown: the comment is available only for TON-based tokens. Its absence is normal, not a wallet malfunction.
The end-to-end timeline of a single send
The figures were taken separately, but they share one scale — from the tap to the moment when it can no longer be cancelled.
stage | how long it takes |
|---|---|
signing in the wallet | instant, on your own device |
broadcasting the transaction to the network | seconds |
getting into a block | 3.006 s on average — measured over 1,000 blocks, 19.09.2026 |
the result of the transfer is visible | in that same block |
irreversibility | 19 blocks, about 57 s — measured 19.09.2026, repeated twice in the day |
crediting on the recipient's side | the recipient's policy, not the network's |
A TRON transaction has a shelf life. In the expiration field the wallet sets a hard deadline; according to the TRON documentation as of 19.09.2026 the default is 60 seconds from the timestamp of the last block, though a wallet may set its own. If it does not make it into a block in time, the nodes drop it: it does not “hang in a queue” the way it would on Ethereum.
How to recognise this case: the explorer finds nothing for the hash and the USDT is still on the balance. No transaction exists under that hash, there is nothing to wait for — the transfer is put together and signed again.
The last row of the table carries half the point of this section. The minute to irreversibility is the network's time. How long it takes before the recipient sees the money on their side is set by their own crediting rules, and from the network's side that cannot be measured.
What it actually costs — across 935 successful transfers
The fee does not depend on the amount, but it does depend on what the sender pays with. In the measurement of 19.09.2026 most transfers sit at the bottom end of the scale — here is what that scale is made of.
fee paid | share of transfers | what it means |
|---|---|---|
0 TRX | 46.6% | energy and bandwidth from staking or delegation |
0.345 TRX | 40.9% | energy from staking, bandwidth paid for |
6.4285 TRX | 4.1% | full burn, ordinary transfer |
6.7735 TRX | 2.2% | the same plus bandwidth |
13.0285 TRX | 1.2% | full burn, first USDT to the address |
13.3735 TRX | 0.5% | the same plus bandwidth |
other | 4.5% | partial and non-standard settlements |
The median is 0.345 TRX, the mean 0.9449 TRX, and 8.0% burned the full price. Zero and 0.345 TRX are paid by those whose energy comes from staked TRX: platforms, services, bots. A person with a new wallet pays in full — hence “it took nothing off my friend but it took it off me”.
The doubling is explained by a second table: how much energy those same 935 transfers used.
energy used | how many transfers | what it means |
|---|---|---|
64,285 | 756 | the recipient already has USDT |
130,285 | 177, that is 18.9% | the first USDT to this address |
other | 2 | complex contract calls |
In money as of 19.09.2026: 6.4285 TRX is about $2.17 and 13.0285 TRX about $4.40, at a TRX rate of $0.338. How the fee works on TRON and how Ethereum differs from it — network fees of TRC20 and ERC20.
Since the price does not depend on the amount, its weight changes by orders of magnitude: on a transfer of 20 USDT the ordinary $2.17 takes a tenth of it, on 2,000 USDT a thousandth. Splitting the amount up does not pay.
The fee ceiling: the hidden field through which the network can cut a transfer short
Every TRON contract call has a fee_limit field — the upper limit on how much the sender agrees to spend. The wallet sets it, without the person's involvement, and usually does not show it in the interface. According to the TRON documentation as of 19.09.2026 the default value is zero and the network maximum is 15,000 TRX.
If the ceiling is below the actual spend, the transaction does not run to the end, and the energy used up to that point is not returned. The person sees only a rejection, while the cause sits in a field they never filled in and have never once seen.
Measurement of 19.09.2026 across the same 949 transfers: the median ceiling is 100 TRX, so in most wallets the headroom is enormous. But 5.37% of transfers went out with a ceiling below 13.0285 TRX — below the price of a transfer to an address that has not yet held USDT.
And the caveat without which the conclusion would be wrong: in all thirteen zero-energy rejections the fee_limit was 100 or 1,000 TRX — a low ceiling had nothing to do with them. We did not look at the ceiling of the fourteenth, the single contract rejection. The mechanism does exist; that it has already caught anyone out is not something the measurement shows.
What happens when a transfer does not go through
outcome | how many | share |
|---|---|---|
transfer went through | 935 | 98.53% |
rejection on zero energy | 13 | 1.37% |
contract rejection | 1 | 0.11% |
Measurement of 19.09.2026: ten blocks in a row, about thirty seconds of network time. These are the three values in that slice, not an exhaustive list of the outcomes TRON can return.
The key thing about the thirteen rejections: in each of them exactly zero energy was used and zero TRX was charged. The budget was nil — no staked energy and no TRX to burn. There turned out to be nothing to burn, and the sender lost nothing.
The fourteenth failed transfer works differently, and it must not be rounded in with the thirteen. It is the one contract rejection: 8,624 energy and 0.345 TRX were charged, and the contract's work up to the point of rejection was paid for. With USDT that usually means the balance is smaller than the amount being sent, or the address is on the issuer's blacklist.
You can tell which case is yours from the fee charged: zero energy and zero TRX means an empty TRX balance; energy spent with no transfer means a contract rejection. What to do in the second case: check the USDT balance against the amount being sent, and if it is fine there is no point repeating — the cause is on the token issuer's side.
After a zero-energy rejection: top the wallet up with TRX and send again. Sending again is safe precisely because the first attempt never happened — the token either moved or it did not. This is the one case in this subject where “just send it again” is sound advice.
The honest limit of the measurement: the case where there is TRX on the balance but not enough for the whole spend did not turn up in the sample. How much burns in that case we did not measure.
Thresholds on the receiving side: why a small amount arrives but will not leave
The network sets no minimum at all. The minimum is set by the recipient, and they have two of them — one for receiving and one for withdrawing. Snapshot of 19.09.2026; the tariffs change without notice.
where it is sent | minimum to receive | cost of withdrawing onward |
|---|---|---|
an exchange platform | 10 USDT on TRC20 and on ERC20 | 1.5 USDT to withdraw on TRC20 |
a custodial wallet in Telegram | from 0.003 USDT on TRC20 | 3.5 USDT to withdraw on TRC20 |
a self-custodial account in Telegram | no minimum, but on the TON network | withdrawal to TRON — from 100 USDT |
The receiving minimum and the withdrawal minimum are different figures, and the second can be hundreds of times the first. The wallet will accept 0.003 USDT and show it on the balance, but that amount will not go back out into the network: it is smaller than the wallet's own withdrawal fee.
Hence the rule: before a small transfer, look not at the deposit minimum but at the withdrawal minimum — for the wallet in Telegram that is 1 USDT, plus 3.5 USDT of fee on top. Both figures sit in the “Fees, rates and limits” section of the help; on platforms they are on the same sort of tariffs-and-limits page. If, once the fee has been taken off, what is left falls below the withdrawal threshold, there is no way at all to get the money back out.
Six places where people go wrong, by the cost of the mistake
- The address was taken not from the deposit page, but from an old chat. The one completely irreversible mistake. What to do if the transfer went to the wrong place — sent crypto to the wrong network.
- There is no TRX in the wallet. The commonest reason for a rejection: 13 cases out of 949 in the measurement of 19.09.2026. The transfer does not go, the money stays where it is.
- Sending to an address that has never held USDT. Not a mistake but a doubling of the price, and the only way to allow for it is in advance.
- Sending again “because the first one did not go through”. At its most dangerous when the first one actually did. Hash first, button second.
- Expecting a successful result to mean “the recipient has seen the money”. These are two different events, and the second does not depend on the network.
- An amount below the recipient's minimum. The network will put it through and take the fee, and the recipient will not credit it automatically. Getting it back is possible, but it means a separate support request with evidence, and it is not guaranteed.
How to make sure it arrived
In the wallet you take the hash of the transfer — TxID, not the “order number”. You open the hash in the network's explorer and look at two fields: Result: Successful means the money has gone, Status: CONFIRMED means it is already irreversible.
Reading the whole page is a subject of its own: how to check a transfer on Tronscan. One consequence is enough here: if the result is successful and the recipient cannot see the money, the question is for the recipient, not for the network.
We will state our own interest out loud: we are an exchange service, not a crypto exchange and not a wallet. If the next step after the transfer is exchanging, we have a separate direction for USDT on the TRON network: the address is issued with the network stated explicitly, and you check the transfer the way described above.
Short answers
How long does a USDT TRC20 transfer take?
On the network, seconds. In the measurement of 19.09.2026 a transfer lands in a block in 3.006 s on average and shows its result at that same moment, and it becomes irreversible after 19 blocks, about 57 seconds. When the recipient sees the money is not for the network to decide: those are their crediting rules, and no time can be named for it.
How much does a USDT TRC20 transfer cost?
The price does not depend on the amount being sent. In the measurement of 19.09.2026 the median was 0.345 TRX, 46.6% of senders paid nothing and 8.0% burned the full price: that is 6.43 TRX on an ordinary transfer and 13.03 TRX if the recipient has never held USDT. In dollars on that same day, about $2.17 and $4.40.
Why will my USDT TRC20 not send?
Most often because there is no TRX in the wallet: in the measurement of 19.09.2026 that is how 13 transfers out of 949 ended. The money stays where it is — zero energy used and zero TRX charged. Top the wallet up with TRX and send again: the first attempt never happened, so repeating it is safe.
What is the minimum amount for a USDT TRC20 transfer?
The network sets no minimum; the recipient does — and their receiving minimum is one figure while their withdrawal minimum is another. By the snapshot of 19.09.2026 the wallet in Telegram accepts from 0.003 USDT, its withdrawal minimum is 1 USDT, and the fee for withdrawing to TRON is 3.5 USDT. The sums have to be done on the last two figures.
