← previous blocknext block →recent activity
Analyzing
Block #74,767,112
25 transactions · 15 stateful · 2026-05-15 14:12:42 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,767,112 · 25 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
1w02w13w15w010w213w314w015w417w220w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a4f666d…f5f7
0xd32edf…ff58
9 touches
10 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x7e530544…82db
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x00000000…0015
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
10 conflicts on slot 0x1a4f666d52…43f5f7
Audit this contract →
← previous block·next block →recent activity