← previous blocknext block →recent activity
Analyzing
Block #77,183,137
24 transactions · 13 stateful · 2026-05-26 18:48:04 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #77,183,137 · 24 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
7w012w015w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27e2056a…bbe9
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd996735f…8730
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
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
10 conflicts on slot 0x27e2056a1e…bfbbe9
Audit this contract →
← previous block·next block →recent activity