← previous blocknext block →recent activity

Analyzing

Block #89,773,004

23 transactions · 19 stateful · 2026-07-24 00:22:51 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,773,004  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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…6e6f

0x188d58…ea8e

10 touches
10 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

10 touches
10 conflicts

0x0dfe4809…e880

0xd32edf…ff58

7 touches
6 conflicts

0x3439dfbc…0d03

0x34b655…2a6f

6 touches
3 conflicts

0x391d170b…bd0f

0x3bd359…433a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x9e15d2b7…2823

0x34b655…2a6f

4 touches
1 conflict

0x46cb45de…a567

0x188d58…ea8e

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

10 conflicts on slot 0x01e7b86585…4d6e6f

← previous block·next block →recent activity