← previous blocknext block →recent activity
Analyzing
Block #83,452,297
30 transactions · 21 stateful · 2026-06-24 20:00:38 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,452,297 · 30 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
1w02w13w14w05w112w213w315w016w117w221w222w323w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d26b123…7cc3
0xd32edf…ff58
7 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xb6d6d740…e921
0x1b6862…e19c
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x9ad4d28a…c788
0x34b655…2a6f
4 touches
1 conflict
0xd9f1e40f…09a3
0x3bd359…433a
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
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
6 conflicts on slot 0x6d26b123f3…8b7cc3
Audit this contract →
← previous block·next block →recent activity