← previous blocknext block →recent activity
Analyzing
Block #87,328,850
50 transactions · 37 stateful · 2026-07-12 19:06:19 UTC
Parallelism
86/100
Blocked
59%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,328,850 · 50 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w09w311w412w313w417w522w434w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
12 touches
15 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0x7bc60db5…cbf1
0xd32edf…ff58
11 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
8 touches
6 conflicts
0x28e527c8…c6f2
0x3bd359…433a
6 touches
3 conflicts
0x3071807d…4430
0xdd0a93…ece5
6 touches
3 conflicts
0x78ae17f2…53be
0x000000…012a
6 touches
3 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
15 conflicts on slot 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity