← previous blocknext block →recent activity
Analyzing
Block #85,992,822
20 transactions · 16 stateful · 2026-07-06 14:16:38 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,992,822 · 20 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
1w02w13w24w35w49w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1674b97c…c629
0xd32edf…ff58
9 touches
10 conflicts
0x4a708eae…e5e1
0x065c9d…c394
4 touches
1 conflict
0xba5743c7…21c1
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x9da6e429…074d
0xa6afd3…d132
4 touches
1 conflict
0xfc578b53…9b1f
0xa6afd3…d132
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
10 conflicts on slot 0x1674b97c1a…f5c629
Audit this contract →
← previous block·next block →recent activity