← previous blocknext block →recent activity
Analyzing
Block #86,982,533
30 transactions · 25 stateful · 2026-07-11 04:30:54 UTC
Parallelism
73/100
Blocked
64%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,982,533 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w49w517w621w723w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cd38f11…ba2e
0xd32edf…ff58
15 touches
28 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x1f44bdf9…51aa
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
28 conflicts on slot 0x0cd38f1145…77ba2e
Audit this contract →
← previous block·next block →recent activity