← previous blocknext block →recent activity
Analyzing
Block #102,276,004
25 transactions · 23 stateful · 2026-09-05 20:10:49 UTC
Parallelism
88/100
Blocked
26%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,276,004 · 25 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
1w02w13w04w26w07w111w012w121w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17359e55…7914
0x188d58…ea8e
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1342557a…df31
0x27bc99…9a93
6 touches
3 conflicts
0x38aa1898…fdf5
0xb53c4f…8a01
4 touches
1 conflict
0x8b9e2d47…9675
0x188d58…ea8e
4 touches
1 conflict
0xb3dee783…2711
0x27bc99…9a93
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xa165a1e5…67be
0x754704…b603
4 touches
1 conflict
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 0x17359e55e7…a57914
Audit this contract →
← previous block·next block →recent activity