← previous blocknext block →recent activity
Analyzing
Block #86,802,991
29 transactions · 25 stateful · 2026-07-10 08:30:40 UTC
Parallelism
76/100
Blocked
52%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,802,991 · 29 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
1w02w13w24w35w47w512w620w621w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd053442…4378
0xd32edf…ff58
13 touches
21 conflicts
0xd35bb5ac…3586
0x065c9d…c394
8 touches
6 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…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xd8d828a7…b64a
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 0xbd05344264…314378
Audit this contract →
← previous block·next block →recent activity