← previous blocknext block →recent activity
Analyzing
Block #86,049,413
34 transactions · 28 stateful · 2026-07-06 20:34:44 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
1.03
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,049,413 · 34 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w618w422w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd357a7f…36c8
0xd32edf…ff58
13 touches
21 conflicts
0x513a67c7…3315
0x065c9d…c394
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x0a85a226…83bd
0x1b6862…e19c
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
21 conflicts on slot 0xcd357a7fe1…6436c8
Audit this contract →
← previous block·next block →recent activity