← previous blocknext block →recent activity
Analyzing
Block #80,265,189
18 transactions · 14 stateful · 2026-06-10 01:36:48 UTC
Parallelism
83/100
Blocked
21%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,265,189 · 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
1w02w13w25w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dd1db39…a994
0x188d58…ea8e
4 touches
1 conflict
0x4dd1db39…a995
0x188d58…ea8e
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x2dce5d6b…2172
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xcec54443…ac01
0x0555e3…2b9c
2 touches
0 conflicts
0x66de0ce3…337a
0x188d58…ea8e
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 0x4dd1db394e…28a994
Audit this contract →
← previous block·next block →recent activity