← previous blocknext block →recent activity
Analyzing
Block #107,640,342
58 transactions · 52 stateful · 2026-09-24 15:15:11 UTC
Parallelism
69/100
Blocked
75%
Avg conflicts / tx
3.55
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #107,640,342 · 58 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w28w110w211w313w121w622w723w824w925w1028w1129w1231w132w1353w1254w1455w1556w1657w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79867a53…34d6
0xd32edf…ff58
31 touches
120 conflicts
0x00000000…001b
0x1b6862…e19c
22 touches
55 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…0012
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
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: FastLane: FastLaneAuctionHandler
120 conflicts on slot 0x79867a5347…8934d6
Audit this contract →
← previous block·next block →recent activity