← previous blocknext block →recent activity
Analyzing
Block #108,840,916
36 transactions · 32 stateful · 2026-09-28 20:01:55 UTC
Parallelism
44/100
Blocked
78%
Avg conflicts / tx
5.64
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #108,840,916 · 36 txs across 20 waves · depth 20
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
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w48w59w610w711w812w913w1014w1115w1216w1317w1418w1519w1620w1721w1822w19
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa701c64f…a2f4
0xd32edf…ff58
39 touches
190 conflicts
0xada193dc…5c7c
0x1b6862…e19c
28 touches
91 conflicts
0x00000000…0013
0x1b6862…e19c
28 touches
91 conflicts
0x00000000…0015
0x1b6862…e19c
28 touches
91 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
24 touches
66 conflicts
0x6f0f03f8…f3de
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…001b
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…002b
0x1b6862…e19c
24 touches
66 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
190 conflicts on slot 0xa701c64ff5…4ba2f4
Audit this contract →
← previous block·next block →recent activity