← previous blocknext block →recent activity
Analyzing
Block #85,912,294
14 transactions · 13 stateful · 2026-07-06 05:19:15 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,912,294 · 14 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
1w03w15w06w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x025e18da…8a5c
0x188d58…ea8e
4 touches
1 conflict
0xbbd6770e…b4ca
0x440a15…6f31
4 touches
1 conflict
0x61dbd4bd…c573
0x7db552…cc3e
4 touches
1 conflict
0x025e18da…8a5d
0x188d58…ea8e
4 touches
1 conflict
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0008
0xec03a3…3bc5
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
1 conflict on slot 0x025e18da60…788a5c
Audit this contract →
← previous block·next block →recent activity