← previous blocknext block →recent activity
Analyzing
Block #85,628,956
23 transactions · 21 stateful · 2026-07-04 21:51:05 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,628,956 · 23 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
1w02w13w210w111w213w314w417w319w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7dd1566…36ab
0xd32edf…ff58
9 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x202c03eb…cf33
0xa6afd3…d132
4 touches
1 conflict
0x1211e3b9…214a
0x065c9d…c394
2 touches
0 conflicts
0x7d4071d1…cce8
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
10 conflicts on slot 0xc7dd156628…f736ab
Audit this contract →
← previous block·next block →recent activity