← previous blocknext block →recent activity
Analyzing
Block #85,124,582
18 transactions · 15 stateful · 2026-07-02 13:51:56 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,124,582 · 18 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
1w02w14w010w011w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f7e3b7…e015
0x188d58…ea8e
4 touches
1 conflict
0x00f7e3b7…e016
0x188d58…ea8e
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x1c8a3a66…2a9c
0x34b655…2a6f
4 touches
1 conflict
0x30df7df6…5e74
0x34b655…2a6f
4 touches
1 conflict
0x30fa662a…06e0
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0xaa48195d…ffee
0x34b655…2a6f
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
1 conflict on slot 0x00f7e3b74f…eee015
Audit this contract →
← previous block·next block →recent activity