← previous blocknext block →recent activity
Analyzing
Block #85,848,756
21 transactions · 16 stateful · 2026-07-05 22:16:06 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,848,756 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w410w012w113w014w115w016w517w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6f
0x188d58…ea8e
8 touches
6 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
8 touches
6 conflicts
0xb96aecfb…6646
0xd32edf…ff58
7 touches
6 conflicts
0x54a035dd…16c6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
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 0x01e7b86585…4d6e6f
Audit this contract →
← previous block·next block →recent activity