← previous blocknext block →recent activity
Analyzing
Block #94,051,470
21 transactions · 15 stateful · 2026-08-07 23:30:46 UTC
Parallelism
86/100
Blocked
27%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,051,470 · 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
1w03w05w17w28w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c225409…6fb2
0x188d58…ea8e
6 touches
3 conflicts
0xb10193fc…87f6
0xfbc1f8…8f9e
6 touches
3 conflicts
0x38aa1898…fdf5
0xfbc1f8…8f9e
6 touches
3 conflicts
0x5c225409…6fb4
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
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 0x5c22540942…7a6fb2
Audit this contract →
← previous block·next block →recent activity