← previous blocknext block →recent activity
Analyzing
Block #75,478,341
20 transactions · 14 stateful · 2026-05-18 21:23:52 UTC
Parallelism
75/100
Blocked
64%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,478,341 · 20 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
1w02w13w24w35w08w19w111w217w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe75ce681…ba5f
0x188d58…ea8e
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x3de6d1ce…6cfd
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0004
0x094452…0a09
6 touches
3 conflicts
0xe75ce681…ba61
0x188d58…ea8e
6 touches
3 conflicts
0x51ca3051…0972
0x3bd359…433a
6 touches
3 conflicts
0x9e223b01…38b2
0x3bd359…433a
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 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: Uniswap: PoolManager
6 conflicts on slot 0xe75ce68176…09ba5f
Audit this contract →
← previous block·next block →recent activity