← previous blocknext block →recent activity
Analyzing
Block #84,120,438
98 transactions · 62 stateful · 2026-06-27 22:16:33 UTC
Parallelism
81/100
Blocked
77%
Avg conflicts / tx
3.49
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #84,120,438 · 98 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
1w02w13w24w35w46w57w68w79w810w917w832w1033w1136w1237w1339w1440w1542w1759w1680w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5db4a4cd…4650
0xd32edf…ff58
35 touches
153 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
32 touches
120 conflicts
0x75cdffd8…c217
0x34b655…2a6f
24 touches
66 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
22 touches
55 conflicts
0x19ce481d…6c36
0x34b655…2a6f
22 touches
55 conflicts
0xe02484a6…c32e
0xc8689a…ee79
22 touches
55 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0012
0x1b6862…e19c
20 touches
45 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
153 conflicts on slot 0x5db4a4cd59…2b4650
Audit this contract →
← previous block·next block →recent activity