← previous blocknext block →recent activity

Analyzing

Block #89,774,761

18 transactions · 18 stateful · 2026-07-24 00:31:45 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

1.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,774,761  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6426

0x34b655…2a6f

6 touches
3 conflicts

0x14c4e3ca…edd9

0x34b655…2a6f

4 touches
1 conflict

0x14c4e3ca…edda

0x34b655…2a6f

4 touches
1 conflict

0xe06bbb2e…9416

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

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)

21 conflicts on slot 0x42041feca2…afbd86

← previous block·next block →recent activity