← previous blocknext block →recent activity
Analyzing
Block #106,308,405
11 transactions · 10 stateful · 2026-09-19 23:29:13 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,308,405 · 11 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
1w05w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88413c1a…7783
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x1ff3f5f1…a59d
0x34b655…2a6f
4 touches
1 conflict
0xc4bbc89f…fca8
0x34b655…2a6f
4 touches
1 conflict
0x1a99f155…77b7
0x34b655…2a6f
2 touches
0 conflicts
0x1beab1d2…6b42
0x34b655…2a6f
2 touches
0 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
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
1 conflict on slot 0x88413c1a8a…857783
Audit this contract →
← previous block·next block →recent activity