← previous blocknext block →recent activity
Analyzing
Block #76,436,241
20 transactions · 18 stateful · 2026-05-23 07:55:25 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,436,241 · 20 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
1w02w13w04w05w17w08w19w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0e6c135…ab48
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 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
15 conflicts on slot 0xc0e6c135c2…2dab48
Audit this contract →
← previous block·next block →recent activity