← previous blocknext block →recent activity
Analyzing
Block #85,131,352
30 transactions · 24 stateful · 2026-07-02 14:37:12 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,131,352 · 30 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
1w02w13w25w06w07w19w214w015w016w117w318w119w224w128w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x640e4164…56f1
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x4063c153…d0cb
0x34b655…2a6f
6 touches
3 conflicts
0x587911c7…9e01
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0xf3fbc9b8…ab58
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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
6 conflicts on slot 0x640e4164b3…b756f1
Audit this contract →
← previous block·next block →recent activity