← previous blocknext block →recent activity
Analyzing
Block #106,109,365
27 transactions · 23 stateful · 2026-09-19 06:47:26 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.67
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,109,365 · 27 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
1w02w13w04w16w211w312w413w315w519w620w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbaa018bc…2b2f
0x34b655…2a6f
18 touches
36 conflicts
0x735a86cd…b64d
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x961c0cd9…0937
0x34b655…2a6f
10 touches
10 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
8 touches
6 conflicts
0xf91d37c7…39f1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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 0xbaa018bc62…432b2f
Audit this contract →
← previous block·next block →recent activity