← previous blocknext block →recent activity
Analyzing
Block #108,652,416
17 transactions · 17 stateful · 2026-09-28 04:10:51 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,652,416 · 17 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
3w05w16w07w18w29w310w411w415w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
6 touches
3 conflicts
0x25957369…c648
0x34b655…2a6f
6 touches
3 conflicts
0xfc906557…ae7f
0x34b655…2a6f
4 touches
1 conflict
0x0735cb54…03ec
0x34b655…2a6f
4 touches
1 conflict
0x165ee7ca…5988
0x34b655…2a6f
4 touches
1 conflict
0x37061895…651d
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity