The Energy conumption of the contract caller in one contract trigger.
The number of TRX burned from the contract caller for Energy conumption in one contract trigger.
The total Energy conumption of the contract developer in one contract trigger.
The total Energy conumption of the contract developer and the contract caller combined.
When the user triggers or create the contract, this is used to set the usage limit of the Energy consumption got from burning TRX or freezing TRX, Energy got from freezing TRX will be used first.
When the user triggers or create the contract, this can be used to send TRX to the contract.
For a contract, Resource consumption is composed of two parts, one part is afforded by contract developer and the other part is afforded by contract caller. This is the percentage of the two parts in the Resource consumption.
The usage limit of the Energy consumption of the developer in one contract trigger, should be greater than 0.
The Bandwidth consumption in one contract trigger. (NetFee not included)
The TRX burned for Bandwidth consumption in one contract trigger.
The Bandwidth Points consumed by a transaction is the size of the byte array in this transaction. If the byte array length of a transaction is 100, then the transaction needs to consume 100 Bandwidth Points.
The creation and operation of a smart contract consume CPU resources. It takes time for smart contracts to operate in virtual machines (VMs), and the time consumed in the system is calculated in microseconds. CPU resources are consumed in energy, which means 1 Energy = 1 Microsecond (μs). If a contract takes 100 μs to execute in a VM, it needs to consume 100 Energy.
1 Frozen TRX = 1 TP, TP can be used to vote, 1 TP = 1 vote.
The current block producing Top 27 nodes.