← previous blocknext block →recent activity
Analyzing
Block #109,144,687
20 transactions · 17 stateful · 2026-09-29 21:35:39 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,144,687 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w19w210w311w212w313w415w016w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37d495b8…f153
0x34b655…2a6f
8 touches
6 conflicts
0xf2f8640d…ceb9
0x34b655…2a6f
8 touches
6 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
6 touches
3 conflicts
0xb15c58ec…bd83
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xdacb24f7…56ce
0x34b655…2a6f
6 touches
3 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
6 conflicts on slot 0x37d495b807…7bf153
Audit this contract →
← previous block·next block →recent activity