← previous blocknext block →recent activity
Analyzing
Block #106,470,997
35 transactions · 34 stateful · 2026-09-20 13:07:32 UTC
Parallelism
51/100
Blocked
68%
Avg conflicts / tx
4.4
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,470,997 · 35 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
1w02w16w211w215w116w317w418w519w620w721w822w923w924w1025w1126w1229w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17bb579f…938c
0x34b655…2a6f
26 touches
78 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0x17d87f0d…bfc5
0x34b655…2a6f
20 touches
45 conflicts
0x1b25f260…c429
0x34b655…2a6f
16 touches
28 conflicts
0x4118bd12…924a
0x34b655…2a6f
16 touches
28 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
14 touches
21 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
14 touches
21 conflicts
0x80d639be…fd4a
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
78 conflicts on slot 0x17bb579f2c…21938c
Audit this contract →
← previous block·next block →recent activity