← previous blocknext block →recent activity

Analyzing

Block #89,416,223

19 transactions · 19 stateful · 2026-07-22 11:48:28 UTC

Parallelism

84/100

Blocked

32%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,416,223  ·  19 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

0x55b4e430…44cb

0x754704…b603

6 touches
3 conflicts

0x3818c04c…a633

0x0a2fbf…29b1

6 touches
3 conflicts

0x3818c04c…a634

0x0a2fbf…29b1

6 touches
3 conflicts

0x690c2db9…9a07

0x0a2fbf…29b1

6 touches
3 conflicts

0x690c2db9…9a08

0x0a2fbf…29b1

6 touches
3 conflicts

0x690c2db9…9a0b

0x0a2fbf…29b1

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

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: USDC (USDC)

3 conflicts on slot 0x55b4e430de…d044cb

← previous block·next block →recent activity