← previous blocknext block →recent activity
Analyzing
Block #108,377,357
23 transactions · 23 stateful · 2026-09-27 05:05:59 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,377,357 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w08w19w110w211w312w213w314w415w516w620w121w222w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
10 touches
10 conflicts
0x2130a548…c1de
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
10 touches
10 conflicts
0x94e7f277…471b
0x34b655…2a6f
10 touches
10 conflicts
0xdd97cbd8…d883
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
10 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity