← previous blocknext block →recent activity
Analyzing
Block #80,953,770
11 transactions · 9 stateful · 2026-06-13 06:08:23 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,953,770 · 11 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
1w02w13w25w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96af006e…c053
0xd32edf…ff58
5 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0xed054a79…ea55
0x065c9d…c394
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065d
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
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 0x96af006e7b…b3c053
Audit this contract →
← previous block·next block →recent activity