← previous blocknext block →recent activity
Analyzing
Block #86,076,395
42 transactions · 31 stateful · 2026-07-06 23:34:38 UTC
Parallelism
88/100
Blocked
52%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,076,395 · 42 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w08w111w216w217w018w119w223w324w326w428w331w434w336w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09beabbc…065c
0x188d58…ea8e
8 touches
6 conflicts
0x846f2172…fd54
0x0555e3…2b9c
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x7636dc0b…b1bf
0xd32edf…ff58
7 touches
6 conflicts
0x46cb45de…a566
0x188d58…ea8e
6 touches
3 conflicts
0x0dbf9688…c6cf
0xd18b7e…414b
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5878d5ad…da45
0x188d58…ea8e
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 0x09beabbc92…45065c
Audit this contract →
← previous block·next block →recent activity