← previous blocknext block →recent activity

Analyzing

Block #89,550,965

16 transactions · 16 stateful · 2026-07-23 02:48:39 UTC

Parallelism

69/100

Blocked

44%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,550,965  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1941b441…5889

0x34b655…2a6f

6 touches
3 conflicts

0x861e5aef…d32c

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x35312bd9…5ef1

0x34b655…2a6f

4 touches
1 conflict

0x37773728…f3a4

0x34b655…2a6f

4 touches
1 conflict

0x4d47fb10…c2c4

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity