← previous blocknext block →recent activity
Analyzing
Block #86,917,199
30 transactions · 26 stateful · 2026-07-10 21:14:19 UTC
Parallelism
73/100
Blocked
54%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,917,199 · 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
1w02w13w24w35w49w010w011w112w213w314w415w519w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06572e13…0e61
0xd32edf…ff58
15 touches
28 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xb538c6fa…9aea
0x1b6862…e19c
8 touches
6 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 0x06572e136c…790e61
Audit this contract →
← previous block·next block →recent activity