← previous blocknext block →recent activity
Analyzing
Block #85,508,464
14 transactions · 13 stateful · 2026-07-04 08:28:44 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,508,464 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w311w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd32d5f7a…f7b8
0xd32edf…ff58
7 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x8f478f26…9d56
0x000000…012a
2 touches
0 conflicts
0x9cafc3b6…ee8c
0x000000…012a
2 touches
0 conflicts
0x556d71b4…a24e
0x065c9d…c394
2 touches
0 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
6 conflicts on slot 0xd32d5f7a52…26f7b8
Audit this contract →
← previous block·next block →recent activity