← previous blocknext block →recent activity

Analyzing

Block #89,690,300

14 transactions · 14 stateful · 2026-07-23 17:25:22 UTC

Parallelism

79/100

Blocked

29%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,690,300  ·  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

0x9e70dadd…810d

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc60a1f10…d727

0x34b655…2a6f

4 touches
1 conflict

0xe0e70374…7b06

0x34b655…2a6f

4 touches
1 conflict

0x9a73834c…0f51

0x34b655…2a6f

4 touches
1 conflict

0x2c2db8e9…fdc7

0x34b655…2a6f

4 touches
1 conflict

0x9a73834c…0f52

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 0x9e70dadd35…1b810d

← previous block·next block →recent activity