The comment suggests you planned to add this, and indeed it makes sense. This executes all the commands needed to process a particular block at once which means we can't query data as it is still being updated. This prevents, for example, race conditions when reading data while updating balances per transaction input/output.

The redis crate support for transactions does not seem suitable for our needs and also does not provide methods for the MULTI and EXEC commands required to perform a transaction, for this reason we manually create the commands. MULTI starts the transaction, and all commands that follow it are queued until a EXEC command is sent.

Is there any issues here where something might happen to prevent the EXEC to end the transaction being called?