← previous blocknext block →recent activity
Analyzing
Block #86,180,885
29 transactions · 25 stateful · 2026-07-07 11:11:57 UTC
Parallelism
66/100
Blocked
60%
Avg conflicts / tx
1.28
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,180,885 · 29 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w69w111w715w120w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c90004a…0698
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
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
21 conflicts on slot 0x4c90004a7c…b10698
Audit this contract →
← previous block·next block →recent activity