← previous blocknext block →recent activity
Analyzing
Block #85,273,870
18 transactions · 16 stateful · 2026-07-03 06:26:31 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,273,870 · 18 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
1w02w13w24w38w413w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc52373dd…36b7
0x188d58…ea8e
8 touches
6 conflicts
0xc52373dd…36b8
0x188d58…ea8e
8 touches
6 conflicts
0xbb6b5cc3…4c49
0x103222…7496
8 touches
6 conflicts
0x782b3042…da2c
0x736237…034f
8 touches
6 conflicts
0x0cc11531…1acb
0x000000…012a
8 touches
6 conflicts
0x12309510…0ac2
0x000000…012a
8 touches
6 conflicts
0x8a207991…db77
0x736237…034f
8 touches
6 conflicts
0x0dbf9688…c6cf
0x103222…7496
8 touches
6 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
6 conflicts on slot 0xc52373dd56…6d36b7
Audit this contract →
← previous block·next block →recent activity