← previous blocknext block →recent activity
Analyzing
Block #75,200,333
15 transactions · 13 stateful · 2026-05-17 14:25:35 UTC
Parallelism
60/100
Blocked
46%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,200,333 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33018431…8f5c
0x188d58…ea8e
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x12309510…0ac2
0x000000…012a
10 touches
10 conflicts
0x3b99eb5d…2c09
0x188d58…ea8e
6 touches
3 conflicts
0x33018431…8f5e
0x188d58…ea8e
6 touches
3 conflicts
0x33018431…8f5f
0x188d58…ea8e
6 touches
3 conflicts
0x3b99eb5d…2c0a
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…0005
0x465a0b…3980
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
10 conflicts on slot 0x330184318b…418f5c
Audit this contract →
← previous block·next block →recent activity