← previous blocknext block →recent activity
Analyzing
Block #106,932,561
32 transactions · 31 stateful · 2026-09-22 03:51:37 UTC
Parallelism
66/100
Blocked
68%
Avg conflicts / tx
2.16
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,932,561 · 32 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w18w09w110w211w312w413w514w115w216w217w318w419w620w721w822w923w1030w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
18 touches
36 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0xc7b7704f…ab36
0x34b655…2a6f
16 touches
28 conflicts
0xd4230a60…bd13
0x34b655…2a6f
14 touches
21 conflicts
0xbbb93c5b…db1b
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity