← previous blocknext block →recent activity
Analyzing
Block #74,260,349
15 transactions · 13 stateful · 2026-05-13 05:49:33 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,260,349 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x4dd1db39…a994
0x188d58…ea8e
4 touches
1 conflict
0x4dd1db39…a996
0x188d58…ea8e
4 touches
1 conflict
0x4dd1db39…a997
0x188d58…ea8e
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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
1 conflict on slot 0x01e7b86585…4d6e6f
Audit this contract →
← previous block·next block →recent activity