← previous blocknext block →recent activity
Analyzing
Block #86,493,567
30 transactions · 22 stateful · 2026-07-08 22:00:52 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,493,567 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w221w022w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0f87e30…26e2
0xd32edf…ff58
11 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x7e10454f…4d9e
0xa6afd3…d132
4 touches
1 conflict
0xb43dc900…22f2
0xa6afd3…d132
4 touches
1 conflict
0xd6694ba8…3e5a
0xa6afd3…d132
4 touches
1 conflict
0x13d0d324…7f70
0x065c9d…c394
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
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
15 conflicts on slot 0xf0f87e30a2…bf26e2
Audit this contract →
← previous block·next block →recent activity