← previous blocknext block →recent activity
Analyzing
Block #75,478,188
13 transactions · 7 stateful · 2026-05-18 21:22:49 UTC
Parallelism
85/100
Blocked
14%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,478,188 · 13 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
5w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66de0ce3…337a
0x188d58…ea8e
4 touches
1 conflict
0x66de0ce3…337d
0x188d58…ea8e
4 touches
1 conflict
0x68d20b91…8d3b
0x188d58…ea8e
4 touches
1 conflict
0x68d20b91…8d3c
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0xe406cabe…e36c
0x0555e3…2b9c
2 touches
0 conflicts
0x00000000…0000
0xbad186…74ab
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 0x66de0ce310…5a337a
Audit this contract →
← previous block·next block →recent activity