← previous blocknext block →recent activity
Analyzing
Block #85,972,603
28 transactions · 26 stateful · 2026-07-06 12:01:26 UTC
Parallelism
82/100
Blocked
42%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,972,603 · 28 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
1w02w13w26w39w011w114w315w417w019w220w321w322w424w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ea8fda5…d137
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
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
10 conflicts on slot 0x5ea8fda5ef…aed137
Audit this contract →
← previous block·next block →recent activity