← previous blocknext block →recent activity
Analyzing
Block #74,252,131
18 transactions · 17 stateful · 2026-05-13 04:54:58 UTC
Parallelism
50/100
Blocked
59%
Avg conflicts / tx
2.11
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #74,252,131 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33018431…8f5c
0x188d58…ea8e
18 touches
36 conflicts
0x33018431…8f5d
0x188d58…ea8e
18 touches
36 conflicts
0x54553c5d…7038
0x188d58…ea8e
18 touches
36 conflicts
0x54553c5d…7039
0x188d58…ea8e
18 touches
36 conflicts
0x0d03d41d…305a
0x000000…012a
18 touches
36 conflicts
0x12309510…0ac2
0x000000…012a
18 touches
36 conflicts
0x0dbf9688…c6cf
0x9c82eb…cd90
18 touches
36 conflicts
0x92bbdb1d…3f94
0x000000…012a
18 touches
36 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
36 conflicts on slot 0x330184318b…418f5c
Audit this contract →
← previous block·next block →recent activity