← previous blocknext block →recent activity

Analyzing

Block #83,966,109

20 transactions · 16 stateful · 2026-06-27 05:08:19 UTC

Parallelism

85/100

Blocked

44%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #83,966,109  ·  20 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7c06e2ec…aee7

0x065c9d…c394

4 touches
1 conflict

0xff96dc9b…93d7

0x065c9d…c394

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x482471ad…122f

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

3 conflicts on slot 0x01e7b86585…4d6e6d

← previous block·next block →recent activity