Estimate TRON Bandwidth and Energy
TRON charges bandwidth for every transaction and energy for contract calls like USDT transfers. This guide estimates both by simulating the transaction, so you provision the right energy and avoid a shortfall mid-send. Size energy before payouts and sweeps.
- The TRON transaction you intend to send, built as raw bytes.
- An API key with C2 access for build and simulate.
1Build the TRON transaction
Build the transfer to get the raw payload. A native TRX transfer mainly consumes bandwidth; a TRC-20 transfer also consumes energy.
curl -X POST https://api.1st-node.com/v1/tx/tron/build \
-H "Authorization: Bearer sk_live_..." \
-d '{"from":"TTreas...","to":"TR8h2...","amount":"5000000"}'
> {"raw":"0a02...","asset":"USDT"}2Simulate to read the cost
Simulate the raw transaction; the result reports the bandwidth and energy the transfer will consume so you can size provisioning.
curl -X POST https://api.1st-node.com/v1/tx/tron/simulate \
-H "Authorization: Bearer sk_live_..." \
-d '{"raw":"0a02..."}'
> {"success":true,"energy_used":32000,"bandwidth_used":345}3Provision energy to match
Rent or delegate at least the estimated energy to the sender so the transfer clears without burning TRX, then broadcast.
curl -X POST https://api.1st-node.com/v1/tron/energy/rent \
-H "Authorization: Bearer sk_live_..." \
-d '{"receiver":"TTreas...","amount":32000}'
> {"status":"active","energy":32000}Perguntas frequentes
What is the difference between bandwidth and energy?
Bandwidth covers the transaction's byte size; energy covers contract execution such as a TRC-20 transfer. Simulation reports both so you provision the right resource.
Why estimate before sending?
An energy shortfall makes a USDT transfer fall back to burning TRX or fail. Estimating lets you rent or delegate exactly enough energy first.
Continue lendo
Recarregue, pegue a chave e publique.
Autoatendimento. Pague em cripto ou cartão. Medido por créditos: primitivas pesadas custam mais, as simples são baratas.
Obter chave de API