← previous blocknext block →recent activity
Analyzing
Block #106,801,639
53 transactions · 47 stateful · 2026-09-21 16:52:39 UTC
Parallelism
68/100
Blocked
77%
Avg conflicts / tx
2.49
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,801,639 · 53 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
2w03w14w25w36w07w09w210w421w122w227w328w433w235w736w839w1140w1241w1342w1443w1544w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38594928…2c55
0x34b655…2a6f
18 touches
36 conflicts
0x1b25f260…c429
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xc305358b…1f5f
0x34b655…2a6f
14 touches
21 conflicts
0x24b2ba87…21ff
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0xf5b5f7…6d70
12 touches
15 conflicts
0x07bc58c3…e53b
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
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
36 conflicts on slot 0x385949288b…662c55
Audit this contract →
← previous block·next block →recent activity