← previous blocknext block →recent activity
Analyzing
Block #84,572,948
30 transactions · 21 stateful · 2026-06-30 00:32:38 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,572,948 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w111w414w015w120w421w022w123w527w228w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e8702ab…c245
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xe75cebb6…6b36
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
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
10 conflicts on slot 0x7e8702ab3b…b0c245
Audit this contract →
← previous block·next block →recent activity