← previous blocknext block →recent activity

Analyzing

Block #89,855,269

13 transactions · 13 stateful · 2026-07-24 07:17:52 UTC

Parallelism

69/100

Blocked

31%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,855,269  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x21e273cb…b384

0x34b655…2a6f

6 touches
3 conflicts

0xd51e027e…7c31

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x91b0f8ed…6bd6

0x34b655…2a6f

4 touches
1 conflict

0x91b0f8ed…6bd7

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xb1b58b33…874f

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: Perpl

3 conflicts on slot 0x21e273cb7e…3db384

← previous block·next block →recent activity