← previous blocknext block →recent activity
Analyzing
Block #89,693,503
20 transactions · 18 stateful · 2026-07-23 17:41:31 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,693,503 · 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
1w03w04w15w26w37w411w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8b6e4c2…e20a
0x188d58…ea8e
6 touches
3 conflicts
0x6f845aff…9fc9
0x3bd359…433a
6 touches
3 conflicts
0x062b2598…4e28
0x43cf54…7777
6 touches
3 conflicts
0x0dbf9688…c6cf
0x43cf54…7777
6 touches
3 conflicts
0x00000000…0000
0x4b6ce4…7f37
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0003
0x4b6ce4…7f37
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
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
3 conflicts on slot 0xe8b6e4c2d9…01e20a
Audit this contract →
← previous block·next block →recent activity