← previous blocknext block →recent activity
Analyzing
Block #76,197,249
21 transactions · 15 stateful · 2026-05-22 05:23:58 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,197,249 · 21 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
1w02w13w24w36w47w18w29w010w113w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7250e0d7…0528
0xd32edf…ff58
9 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf85c75bc…00b5
0xa6afd3…d132
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
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 0x7250e0d7a5…8a0528
Audit this contract →
← previous block·next block →recent activity