← previous blocknext block →recent activity
Analyzing
Block #102,561,034
24 transactions · 20 stateful · 2026-09-06 20:15:19 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,561,034 · 24 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
2w03w14w25w36w08w111w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4179e571…03a2
0x188d58…ea8e
8 touches
6 conflicts
0x38aa1898…fdf5
0x6fa61a…ad01
8 touches
6 conflicts
0x47c54221…e548
0x27bc99…9a93
8 touches
6 conflicts
0x1342557a…df31
0x27bc99…9a93
8 touches
6 conflicts
0x17359e55…7914
0x188d58…ea8e
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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 0x4179e571f6…ff03a2
Audit this contract →
← previous block·next block →recent activity