← previous blocknext block →recent activity
Analyzing
Block #84,458,780
10 transactions · 9 stateful · 2026-06-29 11:50:37 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,458,780 · 10 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
1w02w13w04w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98384470…f38b
0xd32edf…ff58
5 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x56785e37…a197
0x065c9d…c394
2 touches
0 conflicts
0x5a1f0878…34a9
0x065c9d…c394
2 touches
0 conflicts
0x9e118825…abd6
0x065c9d…c394
2 touches
0 conflicts
0xacb5e26a…ea08
0x065c9d…c394
2 touches
0 conflicts
0xc85b4fad…5512
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
3 conflicts on slot 0x983844704e…c9f38b
Audit this contract →
← previous block·next block →recent activity