← previous blocknext block →recent activity
Analyzing
Block #101,966,644
11 transactions · 10 stateful · 2026-09-04 18:02:46 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,966,644 · 11 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
1w03w06w17w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab2f6eed…254a
0x188d58…ea8e
6 touches
3 conflicts
0xd06cc746…27e4
0x350035…7777
6 touches
3 conflicts
0xab2f6eed…254c
0x188d58…ea8e
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2eb15031…f48d
0x34b655…2a6f
2 touches
0 conflicts
0x2f133e1b…777e
0x34b655…2a6f
2 touches
0 conflicts
0x39f55750…f784
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 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