FIG. 22 illustrates allocations based on the blockchain data layer 40, according to exemplary embodiments. As this disclosure previously explained, the data layer server 24 receives the private blockchain 20 and generates the data records 38 representing the blockchain data layer 40 (such as the entries 160, entry blocks 162, and/or the directory blocks 150 explained with reference to FIGS. 10-12). The blockchain load balancing mechanism 60 may thus assign the virtual machine 80 based on the number of the entries 160, the entry blocks 162, and/or the directory blocks 150 associated with the private blockchain 20. For example, as the data records 38 are generated, the blockchain load balancing mechanism 60 may determine a rate 220 of generation. That is, as the data records 38 are generated for any private blockchain 20, exemplary embodiments may sum or count the entries 160, the entry blocks 162, and/or the directory blocks 150 that are generated over time (such as per second, per minute, or other interval). The blockchain load balancing mechanism 60, for example, calls or initializes a counter having an initial value (such as zero). At an initial time, the counter commences or starts counting or summing the number of the entries 160, entry blocks 162, and/or the directory blocks 150 (generated within the blockchain data layer 40) that are commonly associated with or reference the private blockchain 20 (perhaps according to the chain ID 154 representing the entity's private cryptocoinage 70). The counter stops counting or incrementing at a final time and exemplary embodiments determine or read the final value or count. Exemplary embodiments may then calculate the rate 220 of generation as the sum or count over time and consult or query the electronic database 180 for the rate 220 of generation. The electronic database 180 may thus define entries that map or associate different rates 220 of generation and/or ranges to their corresponding virtual machines 80. If the database 180 of virtual machines has an entry that matches or satisfies the rate 220 of generation, exemplary embodiments identify the corresponding virtual machine 80. Once the virtual machine 80 is identified, the blockchain load balancing mechanism 60 may direct or assign the private blockchain 20 to the virtual machine 80 for processing.