← previous blocknext block →recent activity

Analyzing

Block #91,417,308

22 transactions · 17 stateful · 2026-07-29 18:38:43 UTC

Parallelism

73/100

Blocked

47%

Avg conflicts / tx

0.77

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,417,308  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0f2d78b1…7363

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xb05cd4f5…73d0

0x2b46c0…1669

4 touches
1 conflict

0xdb067026…9eb8

0x2b46c0…1669

4 touches
1 conflict

0x3a68f769…de0b

0x34b655…2a6f

4 touches
1 conflict

0x418f6232…2de6

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 0x0f2d78b1bb…5e7363

← previous block·next block →recent activity