← previous blocknext block →recent activity
Analyzing
Block #86,836,886
19 transactions · 17 stateful · 2026-07-10 12:17:25 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,836,886 · 19 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
1w02w13w25w06w18w39w210w311w012w113w414w515w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c870c6e…9044
0xd32edf…ff58
7 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xc6a8c250…737c
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
6 conflicts on slot 0x6c870c6ee9…a69044
Audit this contract →
← previous block·next block →recent activity