← previous blocknext block →recent activity
Analyzing
Block #86,324,063
30 transactions · 26 stateful · 2026-07-08 03:08:10 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,324,063 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w29w310w411w514w015w120w422w425w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77038791…1b55
0xd32edf…ff58
9 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c0
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
10 conflicts on slot 0x77038791b0…d71b55
Audit this contract →
← previous block·next block →recent activity