← previous blocknext block →recent activity
Analyzing
Block #85,918,314
13 transactions · 10 stateful · 2026-07-06 05:59:21 UTC
Parallelism
77/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,918,314 · 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
1w02w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8b6e4c2…e20a
0x188d58…ea8e
6 touches
3 conflicts
0x0dbf9688…c6cf
0x43cf54…7777
6 touches
3 conflicts
0x4a4c3d20…bd65
0x3bd359…433a
4 touches
1 conflict
0x0db0aaac…e94d
0x43cf54…7777
4 touches
1 conflict
0x00000000…0000
0x4a92f8…f3d6
4 touches
1 conflict
0xe8b6e4c2…e20c
0x188d58…ea8e
4 touches
1 conflict
0xc6101b5d…4361
0x3bd359…433a
2 touches
0 conflicts
0xe98ef139…c3b6
0x3bd359…433a
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
3 conflicts on slot 0xe8b6e4c2d9…01e20a
Audit this contract →
← previous block·next block →recent activity