← previous blocknext block →recent activity
Analyzing
Block #75,700,720
35 transactions · 25 stateful · 2026-05-19 22:15:33 UTC
Parallelism
89/100
Blocked
36%
Avg conflicts / tx
0.51
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,700,720 · 35 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
3w04w05w06w08w19w011w012w113w214w125w126w227w329w030w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c65a705…e18f
0xd32edf…ff58
7 touches
6 conflicts
0xd025d7d7…f05a
0x3bd359…433a
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x99a21305…dffc
0x2a68ba…90c5
6 touches
3 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 conflicts
0xdfa159d0…1576
0x065c9d…c394
6 touches
3 conflicts
0xc13c1093…9a9d
0x754704…b603
4 touches
1 conflict
0x00000000…0003
0xdd0a93…ece5
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 0x0c65a70512…e9e18f
Audit this contract →
← previous block·next block →recent activity