← previous blocknext block →recent activity
Analyzing
Block #108,609,985
50 transactions · 46 stateful · 2026-09-28 00:37:09 UTC
Parallelism
68/100
Blocked
76%
Avg conflicts / tx
4.18
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #108,609,985 · 50 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w012w320w721w823w926w127w435w136w237w338w439w540w641w742w843w944w1045w1146w1247w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2a6866…cd40
0xd32edf…ff58
31 touches
120 conflicts
0xca841faa…486a
0x34b655…2a6f
22 touches
55 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x398c985c…810b
0x34b655…2a6f
10 touches
10 conflicts
0x1a99f155…77b7
0x34b655…2a6f
8 touches
6 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
8 touches
6 conflicts
0x399a45fd…1312
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: FastLane: FastLaneAuctionHandler
120 conflicts on slot 0x0d2a686629…c3cd40
Audit this contract →
← previous block·next block →recent activity