← previous blocknext block →recent activity
Analyzing
Block #86,961,446
25 transactions · 23 stateful · 2026-07-11 02:10:01 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,961,446 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w49w010w114w015w116w118w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x165d3a74…2568
0xd32edf…ff58
9 touches
10 conflicts
0x4681609f…6493
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
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
10 conflicts on slot 0x165d3a7483…4f2568
Audit this contract →
← previous block·next block →recent activity