← previous blocknext block →recent activity
Analyzing
Block #108,587,141
23 transactions · 20 stateful · 2026-09-27 22:42:08 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,587,141 · 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
1w04w05w110w013w114w215w316w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
6 touches
3 conflicts
0x1950527a…a8a6
0x34b655…2a6f
6 touches
3 conflicts
0x2106fe09…4142
0x34b655…2a6f
6 touches
3 conflicts
0xa0720dfe…2d4d
0x34b655…2a6f
6 touches
3 conflicts
0x2bd71786…2d83
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity