← previous blocknext block →recent activity
Analyzing
Block #79,241,289
21 transactions · 17 stateful · 2026-06-05 07:34:31 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #79,241,289 · 21 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
1w02w14w210w011w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xadbe0d67…56cf
0xd32edf…ff58
5 touches
3 conflicts
0xee0a9ebb…c425
0x0555e3…2b9c
2 touches
0 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x51ca3051…0972
0x3bd359…433a
2 touches
0 conflicts
0x97ff2a31…c5c3
0x3bd359…433a
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
3 conflicts on slot 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity