← previous blocknext block →recent activity
Analyzing
Block #106,380,624
30 transactions · 30 stateful · 2026-09-20 05:32:40 UTC
Parallelism
43/100
Blocked
67%
Avg conflicts / tx
5.23
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,380,624 · 30 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
1w02w13w04w15w26w29w310w412w414w515w616w717w818w919w1020w1121w1222w1323w1424w1525w1626w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2facdba…7a7e
0x34b655…2a6f
34 touches
136 conflicts
0x74f1de76…50bf
0x34b655…2a6f
22 touches
55 conflicts
0x52f43fc9…66c6
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xf9345145…7229
0x34b655…2a6f
14 touches
21 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0xb9b077a8…e029
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
136 conflicts on slot 0xd2facdbaf5…4f7a7e
Audit this contract →
← previous block·next block →recent activity