← previous blocknext block →recent activity
Analyzing
Block #76,083,398
14 transactions · 11 stateful · 2026-05-21 16:45:43 UTC
Parallelism
57/100
Blocked
45%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,083,398 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc662b1cc…fff9
0xd32edf…ff58
7 touches
6 conflicts
0xf3d7a307…4d63
0x065c9d…c394
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x2ce2d49e…d189
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x696a27c8…5847
0x2a68ba…90c5
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 0xc662b1cc70…5dfff9
Audit this contract →
← previous block·next block →recent activity