← previous blocknext block →recent activity
Analyzing
Block #74,959,889
18 transactions · 10 stateful · 2026-05-16 11:39:59 UTC
Parallelism
61/100
Blocked
70%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,959,889 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w614w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x036f9c09…4a4f
0xd32edf…ff58
13 touches
21 conflicts
0xa74cd79c…705a
0x405b63…7777
4 touches
1 conflict
0xd06cc746…27e4
0x405b63…7777
4 touches
1 conflict
0xbcc1b459…f94f
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0xaa5de1…d330
4 touches
1 conflict
0x00000000…0003
0xaa5de1…d330
4 touches
1 conflict
0x00000000…0000
0xaa5de1…d330
4 touches
1 conflict
0x00000000…000c
0x023eb9…b2b4
2 touches
0 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
21 conflicts on slot 0x036f9c098e…dc4a4f
Audit this contract →
← previous block·next block →recent activity