← previous blocknext block →recent activity
Analyzing
Block #109,131,310
22 transactions · 17 stateful · 2026-09-29 20:27:55 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,131,310 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w07w113w015w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3243e72f…1f6d
0x34b655…2a6f
6 touches
3 conflicts
0x76033196…2444
0x34b655…2a6f
6 touches
3 conflicts
0x742e5c25…a6b2
0x34b655…2a6f
6 touches
3 conflicts
0x7499cc33…a306
0x34b655…2a6f
4 touches
1 conflict
0x85e2939a…902a
0x34b655…2a6f
4 touches
1 conflict
0x8796d0f2…9744
0x34b655…2a6f
4 touches
1 conflict
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0x98dd86bb…1edb
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
3 conflicts on slot 0x3243e72f11…1d1f6d
Audit this contract →
← previous block·next block →recent activity