Latest TRON bandwidth price
Bandwidth is metered against the serialized size of a transaction. When an account does not have enough available bandwidth, TRX can be burned at the current chain-defined rate per uncovered byte. The displayed comparison reads that rate from live TRON network parameters and appears only when current network data is available. The rental rate below is the latest settled fill on our own bandwidth order book, quoted in sun per unit per day; it is a market observation, not a guaranteed execution quote.
Prices below are from the most recent settled fills. Executable price and depth depend on eligible live offers.
- Available now
- 0
- Open orders
- 0
- Active sellers
- 0
Prices are in sun per unit per day. 1 TRX = 1,000,000 sun.
Bandwidth is not energy, and the difference is why transfers fail
Energy pays for contract computation; bandwidth covers serialized transaction size. A plain TRX transfer normally needs bandwidth without contract energy, while a USDT transfer is a contract call and can require both resources. Available energy does not imply available bandwidth: check the account's current resources and delegations separately. If bandwidth does not cover the transaction, TRX can be burned at the current chain-defined rate per uncovered byte; the displayed comparison reads that rate from live TRON network parameters and appears only when current network data is available. Renting energy does not cover that bandwidth shortfall.
What the number means
Prices are quoted in sun per bandwidth unit per day, and one unit covers one byte of transaction data. Supported rentals shorter than one day use a one-day billing minimum; supported multi-day rentals are billed for their full term at the applicable rate. The transfer comparison above uses a 345-byte planning estimate and the latest settled price. It is not a guaranteed execution quote: check the live bandwidth book for the selected duration and amount because executable price and depth can differ from the last fill.
Why the price moves differently from energy
Bandwidth and energy trade in separate, resource-partitioned order books, so their liquidity and prices can move independently. The headline bandwidth rate is the latest settled bandwidth fill when live market data is available; rolling statistics summarize settled fills, while the download aggregates completed UTC days. These observations show what traded. For an executable price and available depth, check the live book for the selected resource, duration, and amount rather than applying a fixed ratio.
A note for sellers, stated plainly
Bandwidth and energy returns cannot be compared reliably with a fixed headline percentage. Seller yield depends on settled fill prices, utilisation, live depth and the amount of each resource produced under the network's current staking conditions. The resources trade in separate books, so shifts in stake allocation can change their supply independently. A listing is not a guaranteed fill; check the live book and your realised utilisation before choosing where to allocate stake.
Download the price history
Daily closes, highs, lows and volume from our own order book. Free to use with attribution — this is primary market data, not an aggregate of other vendors’ quotes.
The series starts publishing once the order book has traded for a full day.
Frequently asked questions
My transfer failed and the error mentions bandwidth, not energy. What do I do?
Check the account's current bandwidth and TRX balance. For transaction bytes not covered by available bandwidth, TRX can be burned at the current chain-defined rate per byte. The displayed comparison reads that rate from live TRON network parameters and appears only when current network data is available. You can retain TRX for that network charge or place a bandwidth rental order, but its executable price, fill, and delivery depend on the live bandwidth book and are not guaranteed. Renting energy does not cover a bandwidth shortfall.
How much bandwidth does a transfer need?
About 268 bytes for a plain TRX transfer and about 345 for a USDT TRC-20 transfer are planning estimates, not fixed requirements. Serialized size varies with the transaction, so inspect the transaction when possible and leave headroom rather than sizing to the byte.
Will my account's available bandwidth be enough?
There is no universal transaction count. It depends on the account's current bandwidth, delegations, and each transaction's serialized size. Check the live account state and leave headroom, especially for automated flows. Any bytes not covered by available bandwidth can burn TRX at the current chain-defined per-byte rate. The displayed comparison reads that rate from live TRON network parameters and appears only when current network data is available.
Can I rent energy and bandwidth together?
You can place energy and bandwidth orders through the same marketplace and wallet flow, but they enter separate resource-specific books. Check each live book for its executable price and depth. Either order may remain open, fill partially, or not fill, and delivery timing is not guaranteed. A USDT transfer may require both resources.