← previous blocknext block →recent activity
Analyzing
Block #86,626,041
24 transactions · 21 stateful · 2026-07-09 12:47:38 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,626,041 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w09w110w213w014w116w118w220w521w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8562ab4…0026
0xd32edf…ff58
9 touches
10 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x11998eac…f9a6
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 0xa8562ab412…040026
Audit this contract →
← previous block·next block →recent activity