← previous blocknext block →recent activity
Analyzing
Block #85,172,639
15 transactions · 14 stateful · 2026-07-02 19:12:12 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,172,639 · 15 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
2w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0xd025d7d7…f05a
0x3bd359…433a
4 touches
1 conflict
0xfbad2c6c…0d32
0x188d58…ea8e
2 touches
0 conflicts
0xfbad2c6c…0d34
0x188d58…ea8e
2 touches
0 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x1e7e4246…4872
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 0x01e7b86585…4d6e6e
Audit this contract →
← previous block·next block →recent activity