← previous blocknext block →recent activity

Analyzing

Block #91,547,294

14 transactions · 14 stateful · 2026-07-30 05:33:35 UTC

Parallelism

79/100

Blocked

57%

Avg conflicts / tx

0.86

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,547,294  ·  14 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

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0x48cba2…b48b

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0x53cccb07…d7f0

0x34b655…2a6f

4 touches
1 conflict

0x57330c5d…9973

0x34b655…2a6f

4 touches
1 conflict

0x6e6a8155…9636

0x34b655…2a6f

4 touches
1 conflict

0x8eef368f…aa21

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 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity