← previous blocknext block →recent activity
Analyzing
Block #86,933,200
19 transactions · 17 stateful · 2026-07-10 23:01:18 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,933,200 · 19 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
1w02w13w24w35w49w010w112w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb36d4ac…0f9f
0xd32edf…ff58
9 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xcc13c07b…d7cc
0x34b655…2a6f
4 touches
1 conflict
0xe60f3716…e366
0x065c9d…c394
3 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001d
0x1b6862…e19c
2 touches
0 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
10 conflicts on slot 0xeb36d4ac6d…d50f9f
Audit this contract →
← previous block·next block →recent activity