← previous blocknext block →recent activity
Analyzing
Block #84,186,246
26 transactions · 20 stateful · 2026-06-28 05:34:27 UTC
Parallelism
85/100
Blocked
35%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,186,246 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w012w013w114w219w121w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fa6b280…d407
0xd32edf…ff58
5 touches
3 conflicts
0x07b5c6c6…8869
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x5da4ed2f…283f
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe75cebb6…6b36
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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 0x0fa6b28014…69d407
Audit this contract →
← previous block·next block →recent activity