← previous blocknext block →recent activity
Analyzing
Block #80,123,740
31 transactions · 24 stateful · 2026-06-09 09:53:38 UTC
Parallelism
84/100
Blocked
46%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,123,740 · 31 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
4w05w16w07w18w211w012w013w115w016w117w018w119w220w221w324w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88829600…d74f
0xd32edf…ff58
9 touches
10 conflicts
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xc3483764…f29b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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 0x888296002c…c0d74f
Audit this contract →
← previous block·next block →recent activity