← previous blocknext block →recent activity

Analyzing

Block #90,440,561

7 transactions · 6 stateful · 2026-07-26 08:42:13 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,440,561  ·  7 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

0x81561f70…fefd

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x424934c8…f2f1

0x34b655…2a6f

4 touches
1 conflict

0x4332bc2b…f8c3

0x34b655…2a6f

4 touches
1 conflict

0x59572298…7f94

0x34b655…2a6f

4 touches
1 conflict

0x616a240e…0c47

0x34b655…2a6f

4 touches
1 conflict

0x66bdb4c2…7ea6

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

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 0x81561f70ba…26fefd

← previous block·next block →recent activity