← previous blocknext block →recent activity

Analyzing

Block #75,107,218

22 transactions · 14 stateful · 2026-05-17 04:03:55 UTC

Parallelism

82/100

Blocked

50%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,107,218  ·  22 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x33018431…8f5c

0x188d58…ea8e

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x12309510…0ac2

0x000000…012a

6 touches
3 conflicts

0x33018431…8f5e

0x188d58…ea8e

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5ba4db2b…2f04

0x34b655…2a6f

4 touches
1 conflict

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0x7341d02f…74da

0x34b655…2a6f

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

6 conflicts on slot 0x330184318b…418f5c

← previous block·next block →recent activity