← previous blocknext block →recent activity
Analyzing
Block #82,667,989
20 transactions · 17 stateful · 2026-06-21 04:39:10 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,667,989 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w18w416w017w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c6d4926…cf4d
0xd32edf…ff58
7 touches
6 conflicts
0xac79a0c7…be0f
0x1b6862…e19c
4 touches
1 conflict
0x92339d95…0800
0x0000a8…8888
4 touches
1 conflict
0xf4c9b253…a045
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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 0x0c6d492661…e9cf4d
Audit this contract →
← previous block·next block →recent activity