← previous blocknext block →recent activity
Analyzing
Block #106,235,480
57 transactions · 50 stateful · 2026-09-19 17:22:15 UTC
Parallelism
67/100
Blocked
68%
Avg conflicts / tx
3.11
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #106,235,480 · 57 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w36w17w08w19w211w312w413w515w624w330w731w833w434w235w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
26 touches
78 conflicts
0x1a84e266…4f8a
0x34b655…2a6f
20 touches
45 conflicts
0xeda80791…093e
0x34b655…2a6f
18 touches
36 conflicts
0xa1c8cffd…d2a1
0x34b655…2a6f
14 touches
21 conflicts
0x2257be8c…d019
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity