← previous blocknext block →recent activity

Analyzing

Block #91,779,179

24 transactions · 23 stateful · 2026-07-31 01:00:02 UTC

Parallelism

75/100

Blocked

35%

Avg conflicts / tx

0.58

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,779,179  ·  24 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

0x7e1faa73…bfbf

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x00ddbbf2…4588

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x66a11a3b…0ee9

0xa6afd3…d132

6 touches
3 conflicts

0xa4e9800f…4ab1

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

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 0x7e1faa73db…84bfbf

← previous block·next block →recent activity