← previous blocknext block →recent activity
Analyzing
Block #85,966,931
35 transactions · 29 stateful · 2026-07-06 11:23:39 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,966,931 · 35 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
1w02w13w210w311w412w513w014w016w117w018w125w626w128w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b91a26f…4f48
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x4979282b…2933
0x1b6862…e19c
8 touches
6 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 0x5b91a26f8a…1c4f48
Audit this contract →
← previous block·next block →recent activity