← previous blocknext block →recent activity

Analyzing

Block #89,517,923

14 transactions · 13 stateful · 2026-07-22 23:07:56 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,517,923  ·  14 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

0x42041fec…bd86

0x754704…b603

6 touches
3 conflicts

0x63da8263…7a24

0x34b655…2a6f

4 touches
1 conflict

0x266a6b2c…4376

0x34b655…2a6f

4 touches
1 conflict

0x266a6b2c…4377

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6a2ebbdd…0438

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x94c3b02b…8a4d

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 0x42041feca2…afbd86

← previous block·next block →recent activity