← previous blocknext block →recent activity
Analyzing
Block #106,185,993
47 transactions · 41 stateful · 2026-09-19 13:13:05 UTC
Parallelism
66/100
Blocked
76%
Avg conflicts / tx
3.21
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,185,993 · 47 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w212w313w414w315w416w517w621w822w923w1024w1125w1226w1338w740w942w1143w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3af041d1…6f61
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
14 touches
21 conflicts
0xaa3b4402…74e6
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x8df3e36b…2109
0x34b655…2a6f
10 touches
10 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
45 conflicts on slot 0x3af041d159…956f61
Audit this contract →
← previous block·next block →recent activity