← previous blocknext block →recent activity
Analyzing
Block #86,388,435
38 transactions · 22 stateful · 2026-07-08 10:18:14 UTC
Parallelism
89/100
Blocked
41%
Avg conflicts / tx
0.34
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,388,435 · 38 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w07w09w113w016w126w027w129w231w334w135w236w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f7e3b7…e016
0x188d58…ea8e
6 touches
3 conflicts
0xd025d7d7…f05a
0x3bd359…433a
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0x7ea6a117…f2f2
0x34b655…2a6f
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
3 conflicts on slot 0x00f7e3b74f…eee016
Audit this contract →
← previous block·next block →recent activity