← previous blocknext block →recent activity
Analyzing
Block #99,163,960
10 transactions · 9 stateful · 2026-08-25 22:38:15 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,163,960 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5a4bb2c…f2c7
0x188d58…ea8e
8 touches
6 conflicts
0x38aa1898…fdf5
0x3bd359…433a
8 touches
6 conflicts
0xd06cc746…27e4
0x5ef52d…4343
8 touches
6 conflicts
0xd6dfef8e…4721
0x0eb88f…c0cc
4 touches
1 conflict
0xaecd6ed8…95ad
0x188d58…ea8e
4 touches
1 conflict
0x388d69c4…4288
0x188d58…ea8e
4 touches
1 conflict
0x33450b54…6744
0x188d58…ea8e
4 touches
1 conflict
0xd9a7cef1…1ed5
0x188d58…ea8e
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
6 conflicts on slot 0xa5a4bb2c2d…50f2c7
Audit this contract →
← previous block·next block →recent activity