← previous blocknext block →recent activity
Analyzing
Block #85,899,683
13 transactions · 10 stateful · 2026-07-06 03:55:17 UTC
Parallelism
85/100
Blocked
30%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,899,683 · 13 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
1w02w13w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a07bd1d…c2af
0x188d58…ea8e
4 touches
1 conflict
0x56a919c4…ab49
0x788571…8888
4 touches
1 conflict
0x1e56f6b6…5940
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x6a07bd1d…c2ae
0x188d58…ea8e
4 touches
1 conflict
0x12c6929d…e7db
0x34b655…2a6f
3 touches
1 conflict
0x4d7057a9…1c18
0x34b655…2a6f
2 touches
0 conflicts
0x5e782d17…5317
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 0x6a07bd1d62…20c2af
Audit this contract →
← previous block·next block →recent activity