← previous blocknext block →recent activity
Analyzing
Block #80,825,055
23 transactions · 18 stateful · 2026-06-12 15:50:03 UTC
Parallelism
87/100
Blocked
39%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,825,055 · 23 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
1w02w15w26w27w09w110w216w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dd1db39…a994
0x188d58…ea8e
4 touches
1 conflict
0x9e0e23b5…6910
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x4dd1db39…a996
0x188d58…ea8e
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
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 0x4dd1db394e…28a994
Audit this contract →
← previous block·next block →recent activity