Đang kiểm tra khả năng đọc thành tiếng của trình duyệt…
Bài đọc này hiện có bằng tiếng Anh. Giao diện sử dụng ngôn ngữ bạn đã chọn.
Đọc bản gốc tiếng Anh →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.
Tiến độ được lưu trên thiết bị này.
Thư viện nguồn
Ngày kiểm tra