← previous blocknext block →recent activity
Analyzing
Block #92,056,592
26 transactions · 20 stateful · 2026-08-01 00:15:32 UTC
Parallelism
88/100
Blocked
30%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,056,592 · 26 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
1w02w13w011w112w013w014w115w016w117w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33018431…8f5c
0x188d58…ea8e
4 touches
1 conflict
0x33018431…8f5d
0x188d58…ea8e
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7b55198a…b946
0x34b655…2a6f
4 touches
1 conflict
0x8fdcb946…dc4b
0x34b655…2a6f
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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 0x330184318b…418f5c
Audit this contract →
← previous block·next block →recent activity