← previous blocknext block →recent activity
Analyzing
Block #84,081,875
25 transactions · 17 stateful · 2026-06-27 17:59:30 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,081,875 · 25 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
1w04w15w06w27w111w212w013w316w218w424w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x239530e9…2a1d
0xd32edf…ff58
5 touches
3 conflicts
0x910be0f4…b71c
0x34b655…2a6f
4 touches
1 conflict
0xbaf10ec0…7aef
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x239530e9b2…0c2a1d
Audit this contract →
← previous block·next block →recent activity