← previous blocknext block →recent activity
Analyzing
Block #85,932,935
23 transactions · 19 stateful · 2026-07-06 07:36:52 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,932,935 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w114w016w117w621w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1db88bc6…6f17
0xd32edf…ff58
11 touches
15 conflicts
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbf140d9d…4923
0x34b655…2a6f
4 touches
1 conflict
0xe4397fc2…55c8
0x34b655…2a6f
4 touches
1 conflict
0xe9cc2c06…2441
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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
15 conflicts on slot 0x1db88bc6e3…4b6f17
Audit this contract →
← previous block·next block →recent activity