← previous blocknext block →recent activity
Analyzing
Block #85,196,199
19 transactions · 17 stateful · 2026-07-02 21:49:10 UTC
Parallelism
84/100
Blocked
12%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,196,199 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e70
0x188d58…ea8e
4 touches
1 conflict
0x3d2ff57e…d0e7
0x188d58…ea8e
4 touches
1 conflict
0x3d2ff57e…d0e8
0x188d58…ea8e
4 touches
1 conflict
0x391d170b…bd0f
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
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
3 conflicts on slot 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity