← previous blocknext block →recent activity
Analyzing
Block #74,510,509
17 transactions · 10 stateful · 2026-05-14 09:34:54 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,510,509 · 17 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
1w02w13w25w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33018431…8f5e
0x188d58…ea8e
6 touches
3 conflicts
0x33018431…8f5c
0x188d58…ea8e
6 touches
3 conflicts
0x4aa4f53b…899f
0x188d58…ea8e
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xb16b1bc6…ff8f
0xd32edf…ff58
5 touches
3 conflicts
0x4aa4f53b…89a0
0x188d58…ea8e
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x71e27d05…e427
0x188d58…ea8e
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: Uniswap: PoolManager
3 conflicts on slot 0x330184318b…418f5e
Audit this contract →
← previous block·next block →recent activity