← previous blocknext block →recent activity
Analyzing
Block #102,561,343
26 transactions · 17 stateful · 2026-09-06 20:16:53 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,561,343 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w010w111w212w314w216w017w121w322w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17359e55…7914
0x188d58…ea8e
8 touches
6 conflicts
0xff71c096…8e6f
0x188d58…ea8e
8 touches
6 conflicts
0x0c1fb248…44dc
0x27bc99…9a93
8 touches
6 conflicts
0x1342557a…df31
0x27bc99…9a93
8 touches
6 conflicts
0x38aa1898…fdf5
0x72ef8b…f101
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xada193dc…5c7f
0x1b6862…e19c
6 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
6 conflicts on slot 0x17359e55e7…a57914
Audit this contract →
← previous block·next block →recent activity