## 4 Simulation Setup and Experimental Results
### Improved LEACH Protocol Experimental Results  
Regarding the energy consumption of each node, when we are applying the key sharing in groups and the head node changes when the key conditions for it are given, we can see in the following graphs how they behave. In this simulation, we have used an example cluster containing 50 nodes. In this cluster, 10 rounds of the protocol have been performed. A total of 10% of the nodes in the network have been configured as CH. After the simulation, 37 nodes out of 50 were excluded as they did not reach the minimum energy threshold. Table 5 presents the experimental parameters associated with the sensor nodes used to obtain the simulation results. \begin{table}
\begin{tabular}{c c c c c c c c} \hline
**No. of Threads (Nodes)** & **8** & **16** & **32** & **64** & **128** & **256** & **512** & **1024** \\ \hline Time consumption (ms) & 0.000548 & 0.0011 & 0.001478 & 0.004942 & 0.013898 & 0.19402 & 0.051176 & 0.14292 \\ \hline \end{tabular}
\end{table} 
Table 4: Rekeying operation performance time is calculated in milliseconds. \begin{table}
\begin{tabular}{c c} \hline
**Component** & **Value** \\ \hline Instance & AWS EC2 M5 \\ Processors & Intel Xeon Platinum 8175M 3.1 GHz (AVX-512) \\ Internal RAM & 1 GB \\ Instance store & NVMe SSD \\ Distributed FS & Interplanetary File System \\ \hline \end{tabular}
\end{table} 
Table 3: Physical components of DLT. The result shows the speed-up from the scenario in which we process the status of each CH sequentially to the situation in which we execute up to eight threads. In each scenario, we were able to process up to 10,000 transactions, where a transaction means requests from the CH to the DLT. In order to confirm these analytical findings, we performed MATLAB simulations on a network of 50 and 100 nodes respectively, we changed the number of clusters from 1 to 4, and then ran both protocols for 1500 simulated rounds. The nodes were placed randomly and equally in each cluster, and we made no restrictions on the distance between the nodes and their cluster heads as shown in Figure 6.  
Figure 7 illustrates the difference between the LEACH and modified LEACH routing protocols. The number of dead nodes in the conventional LEACH from round 5 starting up is clearly visible when compared to the proposed protocol. In addition, the last dead node of the proposed protocol extends up to ten rounds, while the last dead node in the original LEACH is in round nine. The enhanced threshold condition in the proposed protocol is mainly responsible for the network's extension stability. Comparisons are made between \begin{table}
\begin{tabular}{c c} \hline \hline
**Definition** & **Average Value** \\ \hline Size of testbed (number of nodes) & 50,100 homogenous \\ Number of base stations (Bs) & 1 \\ Initial energy for each sensor & 0.005 i \\ Radio circuitry energy dissipation, Eelec & 50 inj/bit \\ Energy dissipation of amplifier in free-space, Efs & 10 jp/bit \\ Energy dissipation of amplifier in multipath, Emp & 0.0013 pj/bit \\ Energy consumption for data aggregation, Eda & 5 nj/bit \\ Global testbed area & \(n\times n\) \\ Local area (cluster size) & n/nc \\ Time & 10 rounds \\ Packet size & 400-bits \\ Message size & 328-bits \\ Encryption key length & 256-bits \\ \hline \hline \end{tabular}
\end{table} 
Table 5: Parameters used for proposed improved LEACH protocol. Figure 6: Topology of wireless sensor networks for a 100-node network. proposed protocols for various network sizes to determine the networks' lifespan and the impact of increasing node separation. Figure 8 indicates that the time consumption to compute a key in each round takes less compared to the original LEACH in the network. This is mostly due to the fact that the distance factor and remaining energy are taken into account during the selection of cluster heads. In the proposed protocol, closer nodes are chosen as head nodes more often than nodes that are farther apart. This means that the total amount of time needed for each round is less.