← previous blocknext block →recent activity
Analyzing
Block #86,306,534
16 transactions · 11 stateful · 2026-07-08 01:10:58 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,306,534 · 16 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab2f6eed…254b
0x188d58…ea8e
4 touches
1 conflict
0xab2f6eed…254a
0x188d58…ea8e
4 touches
1 conflict
0xd06cc746…27e4
0x350035…7777
4 touches
1 conflict
0x41b17bc2…b0ff
0xd32edf…ff58
3 touches
1 conflict
0x3f1434d4…1ce1
0x11ed3b…2c96
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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 0xab2f6eed4a…68254b
Audit this contract →
← previous block·next block →recent activity