← previous blocknext block →recent activity
Analyzing
Block #86,802,893
39 transactions · 30 stateful · 2026-07-10 08:30:01 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,802,893 · 39 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
1w02w13w24w35w47w58w517w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x888d3ed2…50e5
0xd32edf…ff58
15 touches
28 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xd35bb5ac…3586
0x065c9d…c394
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
6 touches
3 conflicts
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 0x888d3ed22c…2d50e5
Audit this contract →
← previous block·next block →recent activity