← previous blocknext block →recent activity
Analyzing
Block #84,358,333
25 transactions · 22 stateful · 2026-06-29 00:41:12 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,358,333 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w07w08w19w010w011w112w119w121w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c013edc…3b7c
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0xb7a3240c…dd63
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcb89a818…e7c1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
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
3 conflicts on slot 0x1c013edcbd…4a3b7c
Audit this contract →
← previous block·next block →recent activity