← previous blocknext block →recent activity
Analyzing
Block #75,478,754
8 transactions · 6 stateful · 2026-05-18 21:26:39 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,478,754 · 8 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
1w02w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09beabbc…065c
0x188d58…ea8e
6 touches
3 conflicts
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0x0dbf9688…c6cf
0xd18b7e…414b
4 touches
1 conflict
0x09beabbc…065d
0x188d58…ea8e
4 touches
1 conflict
0x09beabbc…065f
0x188d58…ea8e
4 touches
1 conflict
0xd019a2f4…2528
0x188d58…ea8e
4 touches
1 conflict
0xd019a2f4…2529
0x188d58…ea8e
4 touches
1 conflict
0xe75ce681…ba5f
0x188d58…ea8e
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
3 conflicts on slot 0x09beabbc92…45065c
Audit this contract →
← previous block·next block →recent activity