← previous blocknext block →recent activity
Analyzing
Block #86,056,362
29 transactions · 19 stateful · 2026-07-06 21:21:02 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,056,362 · 29 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
2w03w16w27w38w09w113w218w321w023w425w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94e7a56f…9d7d
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x8a2f9a36…fb4a
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
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
6 conflicts on slot 0x94e7a56f86…239d7d
Audit this contract →
← previous block·next block →recent activity