← previous blocknext block →recent activity
Analyzing
Block #83,493,459
40 transactions · 33 stateful · 2026-06-25 00:35:18 UTC
Parallelism
88/100
Blocked
58%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,493,459 · 40 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w08w19w010w011w112w113w214w215w321w022w123w225w134w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa07cbcef…52b3
0xd32edf…ff58
9 touches
10 conflicts
0x838b57ba…36cc
0x065c9d…c394
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xff96dc9b…93d7
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xa02e5cdd…76b8
0x34b655…2a6f
8 touches
6 conflicts
0xdafcf690…d8f8
0x34b655…2a6f
8 touches
6 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xa07cbcefd0…a652b3
Audit this contract →
← previous block·next block →recent activity