← previous blocknext block →recent activity
Analyzing
Block #84,250,351
18 transactions · 18 stateful · 2026-06-28 12:41:41 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,250,351 · 18 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
1w02w13w24w35w16w012w113w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd511e6dd…cc6e
0xd32edf…ff58
7 touches
6 conflicts
0x00aaec63…d315
0x065c9d…c394
4 touches
1 conflict
0x025843a2…b2a0
0x065c9d…c394
4 touches
1 conflict
0xac33ff75…077b
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
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 0xd511e6dd73…e3cc6e
Audit this contract →
← previous block·next block →recent activity