← previous blocknext block →recent activity
Analyzing
Block #85,854,291
28 transactions · 19 stateful · 2026-07-05 22:53:00 UTC
Parallelism
82/100
Blocked
47%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,854,291 · 28 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
1w02w03w16w17w28w39w211w012w114w015w116w426w027w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cc5a7c6…bd33
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0003
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x8d47c9a4…f121
0x1b6862…e19c
6 touches
3 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 0x3cc5a7c6b1…d9bd33
Audit this contract →
← previous block·next block →recent activity