← previous blocknext block →recent activity
Analyzing
Block #86,251,106
38 transactions · 25 stateful · 2026-07-07 19:01:03 UTC
Parallelism
74/100
Blocked
60%
Avg conflicts / tx
0.95
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,251,106 · 38 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w49w510w612w220w725w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d133fe4…dc4b
0xd32edf…ff58
13 touches
21 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…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x98067f20…59ea
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
21 conflicts on slot 0x0d133fe4be…97dc4b
Audit this contract →
← previous block·next block →recent activity