← previous blocknext block →recent activity
Analyzing
Block #92,569,124
23 transactions · 18 stateful · 2026-08-02 19:13:11 UTC
Parallelism
87/100
Blocked
39%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,569,124 · 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
1w03w06w09w011w012w113w114w115w116w217w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09beabbc…065c
0x188d58…ea8e
4 touches
1 conflict
0x09beabbc…065d
0x188d58…ea8e
4 touches
1 conflict
0x6518075e…2b17
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x05e1eba1…6491
0x34b655…2a6f
4 touches
1 conflict
0x278c4ae5…1639
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
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 0x09beabbc92…45065c
Audit this contract →
← previous block·next block →recent activity