← previous blocknext block →recent activity
Analyzing
Block #84,022,828
32 transactions · 23 stateful · 2026-06-27 11:26:15 UTC
Parallelism
72/100
Blocked
57%
Avg conflicts / tx
1.13
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #84,022,828 · 32 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w617w725w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65ec483d…10a8
0xd32edf…ff58
15 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xd5b10148…e634
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x46d5a052…ff2e
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 0x65ec483d81…c310a8
Audit this contract →
← previous block·next block →recent activity