← previous blocknext block →recent activity
Analyzing
Block #76,031,784
18 transactions · 14 stateful · 2026-05-21 11:01:25 UTC
Parallelism
72/100
Blocked
57%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,031,784 · 18 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
1w02w13w24w35w47w111w114w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5bc8dd5…6886
0xd32edf…ff58
9 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0xa486f342…64d5
0x34b655…2a6f
4 touches
1 conflict
0x1b34a0a0…bd4e
0x065c9d…c394
4 touches
1 conflict
0xda38066f…3bbe
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
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 0xb5bc8dd532…b66886
Audit this contract →
← previous block·next block →recent activity