← previous blocknext block →recent activity
Analyzing
Block #75,478,344
22 transactions · 13 stateful · 2026-05-18 21:23:54 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,478,344 · 22 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
1w02w13w24w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe75ce681…ba5f
0x188d58…ea8e
8 touches
6 conflicts
0xe75ce681…ba61
0x188d58…ea8e
8 touches
6 conflicts
0x0dbf9688…c6cf
0xd18b7e…414b
8 touches
6 conflicts
0x00000000…0022
0xd2634e…53b1
6 touches
3 conflicts
0x969f2d28…4fa2
0x0555e3…2b9c
6 touches
3 conflicts
0x00000000…0003
0xd2634e…53b1
6 touches
3 conflicts
0x00000000…0011
0xd2634e…53b1
6 touches
3 conflicts
0x00000000…001a
0xd2634e…53b1
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
6 conflicts on slot 0xe75ce68176…09ba5f
Audit this contract →
← previous block·next block →recent activity