← previous blocknext block →recent activity
Analyzing
Block #85,895,052
30 transactions · 20 stateful · 2026-07-06 03:24:23 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,895,052 · 30 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
1w02w13w24w35w38w410w011w013w118w422w128w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1910b6d5…44a2
0xd32edf…ff58
9 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
4 touches
1 conflict
0xe75ce681…ba60
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
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 0x1910b6d55a…1444a2
Audit this contract →
← previous block·next block →recent activity