← previous blocknext block →recent activity
Analyzing
Block #85,659,159
31 transactions · 22 stateful · 2026-07-05 01:12:07 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,659,159 · 31 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
1w04w15w06w07w112w115w116w217w318w420w426w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d248e76…d4b5
0xd32edf…ff58
9 touches
10 conflicts
0x5540f956…69e8
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
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…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
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 0x7d248e7670…95d4b5
Audit this contract →
← previous block·next block →recent activity