How does TRON process transactions: signing to finality
TRON wallets sign a transaction and broadcast it to a node; elected Super Representatives add it to a block. Bandwidth or energy covers the fee.
Vahe HakobyanEditor-in-chief
Updated Oct 6, 20263 min readFact-checked
On this page
A TRX transfer and a smart-contract call follow the same path. You need TRX for the fee, a wallet with your private key, and the recipient address.
What to know before you start
Your wallet builds the transaction, signs it with your private key, and sends it to a TRON node. The signature proves your account authorized it without revealing the key. You need TRX for the fee.
How TRON processes a transaction
TRON runs on delegated proof of stake. People who lock TRX gain TRON Power and elect Super Representatives, the block producers who confirm transactions. TRON does not work like Bitcoin, where miners compete.
- 1Broadcast to a nodeYour wallet sends the signed transaction to a TRON node, which shares it with the network.
- 2Super Representatives validateElected block producers check the signature and resources, then add the transaction to a block.
- 3Charge resourcesA basic transfer uses bandwidth; a smart-contract call uses energy. When either is short, TRON burns TRX.
- 4Watch for confirmationLater blocks build on that block. Once enough later blocks confirm it, the transaction is final.
What to do after you send
Every transaction gets a transaction ID, or TXID. A block explorer uses that ID to show the block and the status.
- Copy the transaction ID before you close the wallet.
- Paste the ID into a TRON block explorer.
- Check the token contract address for a TRC-20 transfer, because fake TRON tokens exist.
- Keep your private key and seed phrase offline.
- Treat any request for your seed phrase as theft, not support.
Frequently asked questions
Bandwidth covers basic transfers. Energy is for smart-contract calls, and you get it by staking TRX or renting it.
TRON produces blocks continuously, so a transaction usually appears in a block within seconds. Finality comes after later blocks build on it.
Once a transaction is final, it cannot be reversed. Before inclusion, an unconfirmed transaction can expire and drop out.
State changes roll back, but the bandwidth and energy used are still spent. If resources were short, TRX can be burned.
