← previous blocknext block →recent activity

Analyzing

Block #90,894,617

21 transactions · 19 stateful · 2026-07-27 22:46:53 UTC

Parallelism

71/100

Blocked

37%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,894,617  ·  21 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

0x89678d1b…463e

0xa6afd3…d132

6 touches
3 conflicts

0x0d2de0f6…e6c6

0x34b655…2a6f

6 touches
3 conflicts

0x45ea7a97…bbb3

0x34b655…2a6f

6 touches
3 conflicts

0xac3e4969…39e9

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf9e23360…8ef7

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

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

3 conflicts on slot 0x89678d1b59…5a463e

← previous block·next block →recent activity