← previous blocknext block →recent activity
Analyzing
Block #86,625,512
40 transactions · 28 stateful · 2026-07-09 12:44:06 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,625,512 · 40 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
1w02w03w04w15w06w17w28w211w012w013w118w121w022w126w328w434w235w337w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46cb45de…a566
0x188d58…ea8e
8 touches
6 conflicts
0x46cb45de…a568
0x188d58…ea8e
8 touches
6 conflicts
0x846f2172…fd54
0x0555e3…2b9c
8 touches
6 conflicts
0x8cf0c30f…fd82
0xd32edf…ff58
7 touches
6 conflicts
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0x094452…0a09
4 touches
1 conflict
0x00000000…0003
0x094452…0a09
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 0x46cb45de01…66a566
Audit this contract →
← previous block·next block →recent activity