← previous blocknext block →recent activity

Analyzing

Block #89,586,095

18 transactions · 17 stateful · 2026-07-23 06:43:15 UTC

Parallelism

83/100

Blocked

18%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,586,095  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xff4a358a…762f

0x34b655…2a6f

4 touches
1 conflict

0xbed06974…09df

0x34b655…2a6f

4 touches
1 conflict

0xdc67731c…2e33

0x34b655…2a6f

4 touches
1 conflict

0xfdd31e6b…3b96

0x34b655…2a6f

4 touches
1 conflict

0x0f2d78b1…7363

0x34b655…2a6f

4 touches
1 conflict

0x18b5d6f3…3d29

0x34b655…2a6f

4 touches
1 conflict

0x1f6f8ff8…a5d4

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity