← previous blocknext block →recent activity
Analyzing
Block #86,815,644
23 transactions · 18 stateful · 2026-07-10 09:55:13 UTC
Parallelism
91/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,815,644 · 23 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
1w03w14w08w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f7e3b7…e015
0x188d58…ea8e
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x473054b8…b15e
0x065c9d…c394
4 touches
1 conflict
0x00f7e3b7…e017
0x188d58…ea8e
4 touches
1 conflict
0x3e8c0a88…4bd8
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0004
0x094452…0a09
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 0x00f7e3b74f…eee015
Audit this contract →
← previous block·next block →recent activity