← previous blocknext block →recent activity
Analyzing
Block #86,256,135
27 transactions · 23 stateful · 2026-07-07 19:34:39 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,256,135 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36e9858b…127e
0xd32edf…ff58
15 touches
28 conflicts
0xba5743c7…21bf
0x1b6862…e19c
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0x7be3246e…f89f
0x34b655…2a6f
4 touches
1 conflict
0x9ad5901a…ce7c
0x34b655…2a6f
4 touches
1 conflict
0xb503dcab…7c61
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
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
28 conflicts on slot 0x36e9858b6c…31127e
Audit this contract →
← previous block·next block →recent activity