← previous blocknext block →recent activity
Analyzing
Block #80,465,684
19 transactions · 16 stateful · 2026-06-10 23:52:58 UTC
Parallelism
84/100
Blocked
25%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,465,684 · 19 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
2w03w14w07w010w011w112w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dd1db39…a996
0x188d58…ea8e
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0xa193b154…ffb9
0x065c9d…c394
4 touches
1 conflict
0x4dd1db39…a994
0x188d58…ea8e
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xfb64e9ec…34fd
0x2a68ba…90c5
3 touches
1 conflict
0xd64180ef…9eea
0xd32edf…ff58
3 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 0x4dd1db394e…28a996
Audit this contract →
← previous block·next block →recent activity