← previous blocknext block →recent activity
Analyzing
Block #76,234,929
15 transactions · 13 stateful · 2026-05-22 09:35:12 UTC
Parallelism
73/100
Blocked
54%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,234,929 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w18w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56ccefb0…3527
0xd32edf…ff58
7 touches
6 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x93afca4c…b47f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0x56ccefb030…7e3527
Audit this contract →
← previous block·next block →recent activity