← previous blocknext block →recent activity
Analyzing
Block #105,683,684
28 transactions · 26 stateful · 2026-09-17 19:02:36 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.36
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,683,684 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w110w321w422w523w624w725w126w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4d49e02…390f
0x34b655…2a6f
14 touches
21 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0x16959359…a041
0x34b655…2a6f
6 touches
3 conflicts
0xa9af9157…5a6e
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
21 conflicts on slot 0xe4d49e02a9…a0390f
Audit this contract →
← previous block·next block →recent activity