← previous blocknext block →recent activity
Analyzing
Block #80,502,142
78 transactions · 55 stateful · 2026-06-11 03:55:48 UTC
Parallelism
78/100
Blocked
71%
Avg conflicts / tx
2.13
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #80,502,142 · 78 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w69w710w811w913w1014w1115w1218w1124w1227w1330w1435w1536w1638w1139w140w242w1262w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9d56796…c223
0xd32edf…ff58
25 touches
78 conflicts
0x9a555477…19a8
0x754704…b603
14 touches
21 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
14 touches
21 conflicts
0x00000000…0002
0x63e48b…53f2
14 touches
21 conflicts
0x00000000…0000
0x63e48b…53f2
14 touches
21 conflicts
0x90f07a4f…d932
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0004
0x63e48b…53f2
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 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
78 conflicts on slot 0xb9d56796e1…49c223
Audit this contract →
← previous block·next block →recent activity