← previous blocknext block →recent activity
Analyzing
Block #102,561,172
16 transactions · 16 stateful · 2026-09-06 20:16:01 UTC
Parallelism
75/100
Blocked
19%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,561,172 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d662b5b…07d4
0x188d58…ea8e
8 touches
6 conflicts
0x1342557a…df31
0x27bc99…9a93
8 touches
6 conflicts
0x38aa1898…fdf5
0x3173a8…3801
8 touches
6 conflicts
0x17359e55…7914
0x188d58…ea8e
8 touches
6 conflicts
0x63b62400…2c95
0x27bc99…9a93
7 touches
6 conflicts
0x00f245ce…1e10
0x34b655…2a6f
2 touches
0 conflicts
0x38ffda89…25b9
0x34b655…2a6f
2 touches
0 conflicts
0x55559831…164f
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
6 conflicts on slot 0x5d662b5b5a…ec07d4
Audit this contract →
← previous block·next block →recent activity