← previous blocknext block →recent activity
Analyzing
Block #84,361,040
30 transactions · 26 stateful · 2026-06-29 00:59:17 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,361,040 · 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
1w02w13w24w38w111w012w116w420w122w023w124w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf241af83…5cb7
0xd32edf…ff58
9 touches
10 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x9ba6dc56…5344
0x065c9d…c394
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0xc08384da…ecb7
0x34b655…2a6f
4 touches
1 conflict
0xd33e70b0…1515
0x34b655…2a6f
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
10 conflicts on slot 0xf241af834e…3e5cb7
Audit this contract →
← previous block·next block →recent activity