← previous blocknext block →recent activity

Analyzing

Block #89,389,059

20 transactions · 20 stateful · 2026-07-22 08:46:51 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #89,389,059  ·  20 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

0x21321ef8…bd04

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x91b0f8ed…6bd6

0x34b655…2a6f

6 touches
3 conflicts

0x91b0f8ed…6bd7

0x34b655…2a6f

6 touches
3 conflicts

0xe40c96f3…9ce4

0x34b655…2a6f

6 touches
3 conflicts

0x7a2fc410…c088

0x34b655…2a6f

5 touches
3 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

6 conflicts on slot 0x21321ef8a7…7cbd04

← previous block·next block →recent activity