← previous blocknext block →recent activity
Analyzing
Block #80,249,788
13 transactions · 11 stateful · 2026-06-09 23:54:07 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,249,788 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46cb45de…a568
0x188d58…ea8e
4 touches
1 conflict
0x93378523…b8bb
0x065c9d…c394
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0xc0429b73…871c
0x065c9d…c394
2 touches
0 conflicts
0xcc4b3371…b355
0x065c9d…c394
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 0x46cb45de01…66a568
Audit this contract →
← previous block·next block →recent activity