← previous blocknext block →recent activity

Analyzing

Block #89,696,680

20 transactions · 17 stateful · 2026-07-23 17:57:33 UTC

Parallelism

85/100

Blocked

35%

Avg conflicts / tx

0.55

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,696,680  ·  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

0xddc22bc2…7f7a

0x754704…b603

6 touches
3 conflicts

0x08330b36…ae29

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0dbf9688…c6cf

0x43cf54…7777

6 touches
3 conflicts

0xe8b6e4c2…e20a

0x188d58…ea8e

6 touches
3 conflicts

0xa47b7766…ee6e

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

3 conflicts on slot 0xddc22bc2be…bf7f7a

← previous block·next block →recent activity