← previous blocknext block →recent activity
Analyzing
Block #86,386,180
28 transactions · 24 stateful · 2026-07-08 10:03:11 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,386,180 · 28 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
1w02w13w24w35w47w59w010w117w018w120w123w225w026w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60bc5787…d313
0xd32edf…ff58
9 touches
10 conflicts
0xcd510377…571e
0xee8c0e…1242
6 touches
3 conflicts
0xa980598e…ec52
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0xb02793…e402
6 touches
3 conflicts
0x00000000…0003
0xb02793…e402
6 touches
3 conflicts
0x00000000…0004
0xb02793…e402
6 touches
3 conflicts
0xd4c913d7…343a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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 0x60bc578721…62d313
Audit this contract →
← previous block·next block →recent activity