← previous blocknext block →recent activity
Analyzing
Block #101,991,852
23 transactions · 19 stateful · 2026-09-04 20:10:39 UTC
Parallelism
78/100
Blocked
37%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,991,852 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w011w215w417w018w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab2f6eed…254a
0x188d58…ea8e
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x69017fce…85bd
0x1b6862…e19c
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xab2f6eed…254c
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x49be7877…55e7
0xd32edf…ff58
5 touches
3 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 0xab2f6eed4a…68254a
Audit this contract →
← previous block·next block →recent activity