← previous blocknext block →recent activity
Analyzing
Block #86,102,794
51 transactions · 33 stateful · 2026-07-07 02:30:40 UTC
Parallelism
84/100
Blocked
55%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,102,794 · 51 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w17w28w39w411w514w121w128w629w737w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25a9c0f0…078d
0xd32edf…ff58
15 touches
28 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x46b62326…9b3c
0xa6afd3…d132
6 touches
3 conflicts
0xa19aba84…8922
0xa6afd3…d132
6 touches
3 conflicts
0xacd1b162…bee6
0x34b655…2a6f
4 touches
1 conflict
0xc4cb048e…7562
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
28 conflicts on slot 0x25a9c0f010…21078d
Audit this contract →
← previous block·next block →recent activity