Blockchain consensus method and device

A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:

• receiving, by a first node in a blockchain, first service data;
• determining, by the first node in the blockchain, a corresponding handling time of the first service data;
• storing, by the first node in the blockchain, the first service data comprising the corresponding handling time at a cache, wherein the cache stores a plurality of pieces of additional service data, and wherein each piece of additional service data of the plurality of pieces of additional service data is associated with a respective handling time;
• determining, by the first node in the blockchain, whether a consensus needs to be performed on at least two pieces of service data in the cache;
• in response to a determination that the consensus needs to be performed, selecting, by the first node in the blockchain, the at least two pieces of service data on which the consensus is to be performed according to a sequence that is based on handling times associated with the at least two pieces of service data;
• and
• performing, by the first node in the blockchain, the consensus on the more than one pieces of service data according to the sequence.

A computer-implemented system, comprising:

• one or more computers;
• and
• one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
• receiving, by a first node in a blockchain, first service data;
• determining, by the first node in the blockchain, a corresponding handling time of the first service data;
• storing, by the first node in the blockchain, the first service data comprising the corresponding handling time at a cache, wherein the cache stores a plurality of pieces of additional service data, and wherein each piece of additional service data of the plurality of pieces of additional service data is associated with a respective handling time;
• determining, by the first node in the blockchain, whether a consensus needs to be performed on at least two pieces of service data in the cache;
• in response to a determination that the consensus needs to be performed, selecting, by the first node in the blockchain, the at least two pieces of service data on which the consensus is to be performed according to a sequence that is based on handling times associated with the at least two pieces of service data;
• and
• performing, by the first node in the blockchain, the consensus on the more than one pieces of service data according to the sequence.