← previous blocknext block →recent activity
Analyzing
Block #109,131,945
25 transactions · 18 stateful · 2026-09-29 20:31:07 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,131,945 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w09w110w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x5ab6d8ba…d356
0xd32edf…ff58
5 touches
3 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
4 touches
1 conflict
0x36f921ef…b75f
0x34b655…2a6f
4 touches
1 conflict
0x5969523e…5191
0x34b655…2a6f
4 touches
1 conflict
0x67318be2…6e11
0x34b655…2a6f
4 touches
1 conflict
0x742e5c25…a6b2
0x34b655…2a6f
4 touches
1 conflict
0x7499cc33…a306
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity