← previous blocknext block →recent activity
Analyzing
Block #86,222,412
28 transactions · 18 stateful · 2026-07-07 15:49:18 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,222,412 · 28 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
1w02w13w25w36w311w012w113w414w424w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x201679c7…8e26
0xd32edf…ff58
9 touches
10 conflicts
0x95523e2a…4c01
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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
0x7322fb4a…635f
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 0x201679c7ea…218e26
Audit this contract →
← previous block·next block →recent activity