← previous blocknext block →recent activity

Analyzing

Block #91,136,139

10 transactions · 9 stateful · 2026-07-28 19:02:49 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #91,136,139  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x680fdd59…e84d

0x34b655…2a6f

4 touches
1 conflict

0x6f4e7625…aba5

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0f2d78b1…7363

0x34b655…2a6f

4 touches
1 conflict

0x06e9e386…506d

0x34b655…2a6f

4 touches
1 conflict

0x270bdb93…67df

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x680fdd5929…bce84d

← previous block·next block →recent activity