← previous blocknext block →recent activity

Analyzing

Block #89,744,678

23 transactions · 20 stateful · 2026-07-23 21:59:50 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,744,678  ·  23 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x390dd46c…deef

0x34b655…2a6f

4 touches
1 conflict

0x5e4f0640…4186

0x34b655…2a6f

4 touches
1 conflict

0x8f63f383…6eda

0x34b655…2a6f

4 touches
1 conflict

0x90d127f4…5c92

0x34b655…2a6f

4 touches
1 conflict

0x392a02b5…0019

0x81a224…7777

4 touches
1 conflict

0x224ff7ce…f233

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

6 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity