A blockchain consensus method performed by a target consensus backup node of a blockchain, comprising: receiving, from a consensus master node of the blockchain, a pre-prepare message in a pre-prepare stage of a consensus proposal for at least one pending-consensus transaction in a transaction pool of the consensus master node, wherein the pre-prepare message carries a transaction hash list, and the transaction hash list comprises a transaction hash of the at least one pending-consensus transaction; matching and selecting, from a transaction pool of the target consensus backup node, the at least one pending-consensus transaction corresponding to the transaction hash list, wherein all consensus nodes of the blockchain have the same transaction hash calculation logic; and obtaining, from the transaction pool of the target consensus backup node, transaction information of the matched at least one pending-consensus transaction, thereby executing a process flow of the consensus proposal based on the transaction information, characterized in that the method further comprises: after adding, by the target consensus backup node, a new transaction to the transaction pool of the target consensus backup node, calculating a transaction hash of the new transaction based on the transaction hash calculation logic, and storing a mapping relationship between the new transaction and a corresponding transaction hash thereof; and the step of matching and selecting the at least one pending-consensus transaction corresponding to the transaction hash list comprises: matching and selecting, from the transaction pool of the target consensus backup node, the at least one pending-consensus transaction corresponding to the transaction hash list based on the pre-stored mapping relationship. receiving, from a consensus master node of the blockchain, a pre-prepare message in a pre-prepare stage of a consensus proposal for at least one pending-consensus transaction in a transaction pool of the consensus master node, wherein the pre-prepare message carries a transaction hash list, and the transaction hash list comprises a transaction hash of the at least one pending-consensus transaction; matching and selecting, from a transaction pool of the target consensus backup node, the at least one pending-consensus transaction corresponding to the transaction hash list, wherein all consensus nodes of the blockchain have the same transaction hash calculation logic; and obtaining, from the transaction pool of the target consensus backup node, transaction information of the matched at least one pending-consensus transaction, thereby executing a process flow of the consensus proposal based on the transaction information, characterized in that the method further comprises: after adding, by the target consensus backup node, a new transaction to the transaction pool of the target consensus backup node, calculating a transaction hash of the new transaction based on the transaction hash calculation logic, and storing a mapping relationship between the new transaction and a corresponding transaction hash thereof; and the step of matching and selecting the at least one pending-consensus transaction corresponding to the transaction hash list comprises: matching and selecting, from the transaction pool of the target consensus backup node, the at least one pending-consensus transaction corresponding to the transaction hash list based on the pre-stored mapping relationship. after adding, by the target consensus backup node, a new transaction to the transaction pool of the target consensus backup node, calculating a transaction hash of the new transaction based on the transaction hash calculation logic, and storing a mapping relationship between the new transaction and a corresponding transaction hash thereof; and the step of matching and selecting the at least one pending-consensus transaction corresponding to the transaction hash list comprises: matching and selecting, from the transaction pool of the target consensus backup node, the at least one pending-consensus transaction corresponding to the transaction hash list based on the pre-stored mapping relationship.