← previous blocknext block →recent activity

Analyzing

Block #89,388,409

21 transactions · 18 stateful · 2026-07-22 08:42:30 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #89,388,409  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0f2d78b1…7363

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x45c30d46…47a5

0x34b655…2a6f

6 touches
3 conflicts

0x539ecb5b…871b

0x34b655…2a6f

4 touches
1 conflict

0x5502e1cc…3910

0x34b655…2a6f

4 touches
1 conflict

0x7d02a2c5…9802

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 0x0f2d78b1bb…5e7363

← previous block·next block →recent activity