Before swapping, check the transaction’s estimated Energy cost and keep enough TRX to cover any part your available resources or the contract do not cover. There is no dependable flat fee: the amount depends on the contract work, your account’s resources, and whether the contract shares Energy with you.
- Energy pays for smart contract computation; Bandwidth pays for the transaction’s size.
- Estimate the specific swap transaction, then convert any uncovered Energy to TRX at the current network rate.
- Keep a modest margin because the estimate can change as contract state changes.
What determines the network cost?
A TRON token swap is a smart contract transaction, so it uses Energy as the contract executes and Bandwidth to put the signed transaction on-chain. The Energy depends on the work the contract performs, not simply on the amount of USDT or JST being exchanged.
One swap may call a token contract and a trading contract; a route through multiple pools can add more contract work. The account may pay some or none of the Energy burn if it has staked or delegated Energy, or if the contract’s deployer covers a share. Bandwidth is separate: TRON currently provides 600 free Bandwidth per account per rolling 24-hour period, and the transaction’s byte size determines how much it uses.
If you want the broader explanation of how a TRON swap works, that article covers the process from the wallet. Here, the key cost distinction is that a displayed exchange rate or price impact is about the trade, while Energy and Bandwidth are network resources used to execute it.
How do you estimate the TRX amount?
Start with the estimated Energy for the exact contract call, then check the current Energy price and your available Energy. TRON’s Developer Hub documents simulation through triggerconstantcontract, which estimates Energy without broadcasting a transaction; TronWeb also documents an Energy estimate method, though availability depends on the node.
For an illustrative calculation, suppose a simulation estimates 180,000 Energy and the current chain parameter is 100 sun per Energy. If you have no Energy and no contract coverage, the Energy burn would be 18 TRX: 180,000 × 100 sun, with 1,000,000 sun equal to 1 TRX. The example is arithmetic, not a typical quote for every swap.
Next, check how much Energy your account can use and whether the contract covers part of the cost. The TRON Developer Hub’s Resource Model explains that available staked or delegated Energy is consumed before the remaining cost is burned from TRX. Add any expected Bandwidth burn if your free quota or staked Bandwidth will not cover the transaction.
Why can the final cost differ?
The same token and amount can take different execution paths. A route can involve a different number of contracts, and a contract may use more Energy when its stored state changes; the simulator also reflects the state it reads, which may differ by the time the transaction executes.
For an occasional TRON swap, use the estimate for the actual route and your own wallet address, then leave a small practical margin. A contract transaction also has a fee_limit, a cap on how much TRX the caller can have burned for Energy; a cap that is too low can cause execution to run out of Energy, while a high cap does not mean that amount will automatically be charged.
Before confirming, compare the estimated Energy burn with your available TRX and resources, and make sure you are comfortable with both the network cost and the trade quote. If either has changed since you checked it, review the current estimate before sending.