← previous blocknext block →recent activity

Analyzing

Block #89,384,688

14 transactions · 14 stateful · 2026-07-22 08:17:36 UTC

Parallelism

79/100

Blocked

14%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,384,688  ·  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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x88e771e8…7d4a

0x34b655…2a6f

4 touches
1 conflict

0x8f63f383…6eda

0x34b655…2a6f

4 touches
1 conflict

0xb5c7c6aa…fdba

0x34b655…2a6f

4 touches
1 conflict

0x34d95d94…3a16

0x34b655…2a6f

2 touches
0 conflicts

0x4a5956ef…e226

0x34b655…2a6f

2 touches
0 conflicts

0x5af10b50…8d5c

0x34b655…2a6f

2 touches
0 conflicts

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 0xc824469a90…af6425

← previous block·next block →recent activity