← previous blocknext block →recent activity
Analyzing
Block #84,972,708
30 transactions · 25 stateful · 2026-07-01 20:56:21 UTC
Parallelism
87/100
Blocked
28%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,972,708 · 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
1w02w13w25w06w17w012w013w120w221w322w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35ffe7ca…d092
0xd32edf…ff58
7 touches
6 conflicts
0x08943ea2…ed03
0x754704…b603
6 touches
3 conflicts
0xd77e90ec…8c04
0x3bd359…433a
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
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 0x35ffe7ca61…e1d092
Audit this contract →
← previous block·next block →recent activity