← previous blocknext block →recent activity
Analyzing
Block #75,745,728
18 transactions · 14 stateful · 2026-05-20 03:15:16 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,745,728 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w212w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33018431…8f5c
0x188d58…ea8e
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x12309510…0ac2
0x000000…012a
6 touches
3 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x1d77e2ec…d455
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6a9e408e…3721
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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: Uniswap: PoolManager
3 conflicts on slot 0x330184318b…418f5c
Audit this contract →
← previous block·next block →recent activity