← previous blocknext block →recent activity
Analyzing
Block #74,919,627
30 transactions · 17 stateful · 2026-05-16 07:10:17 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,919,627 · 30 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
1w02w13w25w37w412w013w017w022w125w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
8 touches
6 conflicts
0x00000000…0000
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0002
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0004
0xd5b70d…615b
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
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
10 conflicts on slot 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity