← previous blocknext block →recent activity
Analyzing
Block #99,164,095
8 transactions · 8 stateful · 2026-08-25 22:38:56 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,164,095 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9a7cef1…1ed5
0x188d58…ea8e
4 touches
1 conflict
0xa5a4bb2c…f2c7
0x0eb88f…c0cc
4 touches
1 conflict
0x388d69c4…4288
0x188d58…ea8e
4 touches
1 conflict
0x38aa1898…fdf5
0x3bd359…433a
4 touches
1 conflict
0xa5a4bb2c…f2c7
0x188d58…ea8e
4 touches
1 conflict
0xd06cc746…27e4
0x5ef52d…4343
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x4eff5225…9bb1
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xd9a7cef10b…5c1ed5
Audit this contract →
← previous block·next block →recent activity