← previous blocknext block →recent activity
Analyzing
Block #105,844,021
41 transactions · 39 stateful · 2026-09-18 08:30:57 UTC
Parallelism
59/100
Blocked
62%
Avg conflicts / tx
2.9
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,844,021 · 41 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w111w012w115w016w117w218w319w420w521w622w723w824w925w427w1136w137w238w339w440w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd7f5b55…4994
0x34b655…2a6f
24 touches
66 conflicts
0x577fb105…7618
0x34b655…2a6f
20 touches
45 conflicts
0x42522e76…2592
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
16 touches
28 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
14 touches
21 conflicts
0x0efc210e…70ab
0x34b655…2a6f
14 touches
21 conflicts
0x63feb930…1c80
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 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
66 conflicts on slot 0xfd7f5b557f…f74994
Audit this contract →
← previous block·next block →recent activity