← previous blocknext block →recent activity
Analyzing
Block #73,374,620
20 transactions · 14 stateful · 2026-05-09 03:17:00 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,374,620 · 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
1w02w15w07w29w112w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
8 touches
6 conflicts
0x4cabef59…9ced
0xd32edf…ff58
7 touches
6 conflicts
0x6af306bb…2e81
0x3bd359…433a
4 touches
1 conflict
0xf91b744e…9117
0x754704…b603
4 touches
1 conflict
0x1c354dc0…96de
0x754704…b603
4 touches
1 conflict
0x8db1e0f2…2fcf
0x34b655…2a6f
2 touches
0 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 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity