← previous blocknext block →recent activity
Analyzing
Block #86,081,300
26 transactions · 22 stateful · 2026-07-07 00:07:14 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,081,300 · 26 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
1w02w13w25w06w313w315w016w120w423w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f033b6…1651
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x6637e421…af93
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
6 conflicts on slot 0x63f033b624…991651
Audit this contract →
← previous block·next block →recent activity