← previous blocknext block →recent activity
Analyzing
Block #109,143,127
17 transactions · 14 stateful · 2026-09-29 21:27:23 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,143,127 · 17 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
1w05w06w110w215w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0e59c55…2dca
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xd05dc1cb…363b
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xd7b5087e…60a2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb8dc136f…fb16
0xc8689a…ee79
4 touches
1 conflict
0xcb45d9d6…cb81
0x1b6862…e19c
2 touches
0 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
3 conflicts on slot 0xd0e59c55f8…a92dca
Audit this contract →
← previous block·next block →recent activity