← previous blocknext block →recent activity

Analyzing

Block #91,608,312

7 transactions · 6 stateful · 2026-07-30 10:40:31 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,608,312  ·  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

0xe57232b3…0fbf

0x34b655…2a6f

4 touches
1 conflict

0x00bbd28c…e227

0x34b655…2a6f

4 touches
1 conflict

0x41c16dcc…78ab

0x34b655…2a6f

4 touches
1 conflict

0x52e86cc7…ae22

0x34b655…2a6f

4 touches
1 conflict

0xb10b0390…fa46

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

2 touches
0 conflicts

0x3f8c4e42…bb85

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 0xe57232b3f8…130fbf

← previous block·next block →recent activity