กำลังตรวจสอบว่าเบราว์เซอร์รองรับการอ่านออกเสียงหรือไม่…
บทอ่านนี้มีเป็นภาษาอังกฤษในขณะนี้ ส่วนติดต่อใช้ภาษาที่คุณเลือก
อ่านต้นฉบับภาษาอังกฤษ →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.
ความคืบหน้าจะบันทึกไว้บนอุปกรณ์นี้
ห้องสมุดแหล่งอ้างอิง
ตรวจสอบ