← previous blocknext block →recent activity

Analyzing

Block #89,580,091

22 transactions · 18 stateful · 2026-07-23 06:03:08 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,580,091  ·  22 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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x42041fec…bd86

0x754704…b603

4 touches
1 conflict

0xf06fce24…887d

0x34b655…2a6f

4 touches
1 conflict

0xf1cc9519…84c1

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x19b2e42c…dc75

0x40c49f…2af0

4 touches
1 conflict

0x3b75439c…1d4b

0x40c49f…2af0

4 touches
1 conflict

0xa8dd5634…a2e6

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

6 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity