← previous blocknext block →recent activity
Analyzing
Block #86,299,745
24 transactions · 22 stateful · 2026-07-08 00:25:36 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1.25
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,299,745 · 24 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
1w02w13w24w35w46w414w515w619w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5ae5ca7…90c8
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x18cf3003…51d1
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
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 0xc5ae5ca731…5490c8
Audit this contract →
← previous block·next block →recent activity