← previous blocknext block →recent activity
Analyzing
Block #108,539,540
14 transactions · 14 stateful · 2026-09-27 18:42:19 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,539,540 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w06w17w18w29w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe54b350b…a0a3
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x87b3c188…6ea2
0x34b655…2a6f
4 touches
1 conflict
0x89e039e5…2a90
0x34b655…2a6f
4 touches
1 conflict
0x99714b34…f5c1
0x34b655…2a6f
4 touches
1 conflict
0x9b419d78…018b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
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
1 conflict on slot 0xe54b350be2…7ba0a3
Audit this contract →
← previous block·next block →recent activity