← previous blocknext block →recent activity
Analyzing
Block #106,396,926
31 transactions · 29 stateful · 2026-09-20 06:54:43 UTC
Parallelism
45/100
Blocked
66%
Avg conflicts / tx
3.68
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,396,926 · 31 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
1w02w13w26w312w413w514w615w716w817w920w1021w1122w1223w1324w1325w1426w1527w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d37224b…5ba8
0x34b655…2a6f
24 touches
66 conflicts
0x3b53436c…2ec3
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x8379d944…cc17
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x4984f7be…d515
0x34b655…2a6f
12 touches
15 conflicts
0x0463db49…5d05
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 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 0x6d37224bf2…725ba8
Audit this contract →
← previous block·next block →recent activity