← previous blocknext block →recent activity

Analyzing

Block #90,484,622

17 transactions · 16 stateful · 2026-07-26 12:24:15 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,484,622  ·  17 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…003d

0xa6afd3…d132

10 touches
10 conflicts

0x529e53cf…38e4

0xa6afd3…d132

10 touches
10 conflicts

0xc6b1d981…1be2

0xa6afd3…d132

10 touches
10 conflicts

0x745952b2…d90c

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x989252a1…d812

0xa6afd3…d132

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x322fb0e8…962d

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: Kuru Exchange: Market-WETH/USDC

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity