← previous blocknext block →recent activity
Analyzing
Block #76,437,960
25 transactions · 16 stateful · 2026-05-23 08:06:53 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,437,960 · 25 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
2w03w14w25w38w09w411w115w2
- 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
8 touches
6 conflicts
0x55bc696d…7036
0xdd0a93…ece5
6 touches
3 conflicts
0x28e527c8…c6f2
0x3bd359…433a
6 touches
3 conflicts
0x78ae17f2…53be
0x000000…012a
6 touches
3 conflicts
0x00000000…0004
0xdd0a93…ece5
6 touches
3 conflicts
0x00000000…0005
0xdd0a93…ece5
6 touches
3 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
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
10 conflicts on slot 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity