இந்த உலாவியின் உரை வாசிப்பு வசதியைச் சரிபார்க்கிறது…
இந்த வாசிப்பு தற்போது ஆங்கிலத்தில் கிடைக்கிறது. இடைமுகம் நீங்கள் தேர்ந்தெடுத்த மொழியைப் பயன்படுத்துகிறது.
ஆங்கில மூலத்தை வாசிக்கவும் →Read the receipt, not just the hash
Distinguish submission, execution and solidified state while inspecting resource costs.
A returned transaction ID is a reference to investigate. It is not proof that a contract action succeeded.
Follow the confirmation stages
TRON distinguishes broadcast acceptance, inclusion, the execution receipt and solidified state. The transaction body alone cannot prove business success. In a public explorer, inspect the receipt's result, contract address and resource fields; when final-state assurance matters, check whether the transaction has reached solidified state.
Read limits and actual costs separately
Available resources can cover some work; insufficient resources can require burning TRX. For contract calls, fee_limit caps the available Energy budget, including applicable staked resources, rather than simply stating a fixed amount of TRX to burn. Compare the estimate, limit and actual receipt. Do not assume a failed call was free.
Observe one public receipt
Use a historical TRONSCAN transaction. No wallet connection is required.
- Confirm the network and find its transaction ID and execution result.
- Record available Bandwidth, Energy and fee fields without inventing missing data.
- Separate the contract action's result from the page's confirmation or solidification information.
Submission, execution and final-state confidence are distinct observations.
Keep the original transaction ID and read its receipt before deciding what happened.
உங்கள் முன்னேற்றம் இந்தச் சாதனத்தில் சேமிக்கப்படும்.
ஆதார நூலகம்
மதிப்பாய்வு செய்யப்பட்டது