← previous blocknext block →recent activity

Analyzing

Block #89,703,160

23 transactions · 17 stateful · 2026-07-23 18:30:10 UTC

Parallelism

87/100

Blocked

35%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,703,160  ·  23 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

0xa86351b8…2c5a

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x2794fd34…c82f

0x34b655…2a6f

4 touches
1 conflict

0x4175950a…1dfe

0x34b655…2a6f

4 touches
1 conflict

0x5af10b50…8d5c

0x34b655…2a6f

4 touches
1 conflict

0x5ea9eca9…22a6

0x34b655…2a6f

4 touches
1 conflict

0x5ea9eca9…22a7

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 0xa86351b861…d52c5a

← previous block·next block →recent activity