← previous blocknext block →recent activity

Analyzing

Block #89,667,326

18 transactions · 17 stateful · 2026-07-23 15:28:47 UTC

Parallelism

78/100

Blocked

53%

Avg conflicts / tx

0.72

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,667,326  ·  18 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

0x861e5aef…d32c

0x34b655…2a6f

6 touches
3 conflicts

0x43fd3667…094b

0x34b655…2a6f

6 touches
3 conflicts

0x691fa1b0…5b08

0x34b655…2a6f

6 touches
3 conflicts

0xfb8c6cf4…01ee

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xdb067026…9eb8

0x2b46c0…1669

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x6e1d16c5…2d3e

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 0x861e5aeffa…5cd32c

← previous block·next block →recent activity