← previous blocknext block →recent activity
Analyzing
Block #85,973,363
40 transactions · 23 stateful · 2026-07-06 12:06:30 UTC
Parallelism
88/100
Blocked
48%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,973,363 · 40 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w08w110w311w017w123w230w431w035w136w238w239w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4595f204…4a97
0xd32edf…ff58
9 touches
10 conflicts
0x2406ccf7…c1cb
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x2ce2d49e…d187
0x1b6862…e19c
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
10 conflicts on slot 0x4595f2041d…b54a97
Audit this contract →
← previous block·next block →recent activity