← previous blocknext block →recent activity
Analyzing
Block #83,036,961
17 transactions · 13 stateful · 2026-06-22 21:44:57 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,036,961 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w17w29w314w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09beabbc…065c
0x188d58…ea8e
6 touches
3 conflicts
0x09beabbc…065e
0x188d58…ea8e
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0dbf9688…c6cf
0xd18b7e…414b
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb87
0x1b6862…e19c
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
3 conflicts on slot 0x09beabbc92…45065c
Audit this contract →
← previous block·next block →recent activity