← previous blocknext block →recent activity
Analyzing
Block #75,845,179
21 transactions · 13 stateful · 2026-05-20 14:18:22 UTC
Parallelism
90/100
Blocked
31%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,845,179 · 21 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w09w112w114w015w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x479938b6…4691
0xd32edf…ff58
3 touches
1 conflict
0x4dd1db39…a996
0x188d58…ea8e
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
1 conflict on slot 0x01e7b86585…4d6e6f
Audit this contract →
← previous block·next block →recent activity