← previous blocknext block →recent activity
Analyzing
Block #84,330,002
20 transactions · 13 stateful · 2026-06-28 21:32:20 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,330,002 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w114w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ba262ff…c877
0xd32edf…ff58
5 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xc05b880b…7746
0xa6afd3…d132
4 touches
1 conflict
0xa3332349…f62a
0xa6afd3…d132
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0019
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0029
0x1b6862…e19c
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
3 conflicts on slot 0x5ba262ffab…e7c877
Audit this contract →
← previous block·next block →recent activity