← previous blocknext block →recent activity
Analyzing
Block #86,246,924
25 transactions · 17 stateful · 2026-07-07 18:33:04 UTC
Parallelism
72/100
Blocked
65%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,246,924 · 25 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
1w02w13w24w35w46w57w612w215w017w118w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff84de02…dd28
0xd32edf…ff58
13 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd4c913d7…343f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x2267f8c4…a571
0x34b655…2a6f
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
21 conflicts on slot 0xff84de026b…c5dd28
Audit this contract →
← previous block·next block →recent activity