← previous blocknext block →recent activity
Analyzing
Block #85,145,221
13 transactions · 10 stateful · 2026-07-02 16:09:44 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,145,221 · 13 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
1w02w13w15w27w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x107b5402…dfc9
0x188d58…ea8e
4 touches
1 conflict
0x107b5402…dfc7
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x7b4e7a72…9a23
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0019
0x1b6862…e19c
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 0x107b5402bd…55dfc9
Audit this contract →
← previous block·next block →recent activity