Transaction Nonce – Are Transactions Mined in Nonce Order from One Account?

contract-invocationminingprotocolsolidity

Discussion in another thread raises an interesting point. how many transactions could be included in a new block from the same account?

Since

miners can opt to omit a known transaction from the block they're
working on
miners don't have simultaneous knowledge of pending
transactions

is it correct to conclude that transactions submitted from the same node more or less simultaneously (and with ascending nonce) are not necessarily mined in nonce order?

Best Answer

The protocol requires that transactions from a single account are executed in nonce order. It's still possible for an account to have many pending transactions, and as long as the nonces are contiguous, a miner can include as many of them as desired in a single block, as long as they're executed in order.

There's no guarantee of ordering of transactions issued by different accounts.

Related Solutions

Solidity Random Number Generation – Pseudo Random Number in Same Block

You can use an incrementing nonce each time a number is generated. This would have a large effect on the hash output.

Random 0-100 Example:

contract Random {
    uint nonce;


    function random() internal returns (uint) {
    uint random = uint(keccak256(now, msg.sender, nonce)) % 100;
    nonce++;
    return random;
    }

    function getRandom() external view returns (uint) {
        return random();
    }
}

Best Answer

Related Solutions

Solidity Random Number Generation – Pseudo Random Number in Same Block

Related Topic