← previous blocknext block →recent activity
Analyzing
Block #75,478,889
20 transactions · 15 stateful · 2026-05-18 21:27:35 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,478,889 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w010w011w112w217w318w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe75ce681…ba5f
0x188d58…ea8e
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x0dbf9688…c6cf
0xd18b7e…414b
10 touches
10 conflicts
0x00000000…0002
0x4aa799…8148
6 touches
3 conflicts
0x00000000…0004
0x4aa799…8148
6 touches
3 conflicts
0x846f2172…fd54
0x0555e3…2b9c
6 touches
3 conflicts
0xe75ce681…ba61
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…0000
0x4aa799…8148
6 touches
3 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
10 conflicts on slot 0xe75ce68176…09ba5f
Audit this contract →
← previous block·next block →recent activity