← previous blocknext block →recent activity
Analyzing
Block #99,163,770
25 transactions · 24 stateful · 2026-08-25 22:37:18 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1.8
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,163,770 · 25 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
0x388d69c4…4288
0x188d58…ea8e
18 touches
36 conflicts
0xa5a4bb2c…f2c7
0x0eb88f…c0cc
18 touches
36 conflicts
0xa5a4bb2c…f2c7
0x188d58…ea8e
18 touches
36 conflicts
0xd9a7cef1…1ed5
0x188d58…ea8e
18 touches
36 conflicts
0xd06cc746…27e4
0x5ef52d…4343
18 touches
36 conflicts
0x38aa1898…fdf5
0x3bd359…433a
18 touches
36 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0xbd590df7…9891
0x34b655…2a6f
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
36 conflicts on slot 0x388d69c4cf…af4288
Audit this contract →
← previous block·next block →recent activity