← previous blocknext block →recent activity

Analyzing

Block #91,074,423

24 transactions · 20 stateful · 2026-07-28 13:52:16 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.42

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,074,423  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x35a9f06c…7689

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x1a287886…0266

0xa6afd3…d132

4 touches
1 conflict

0x8369eecf…1193

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xd0fd6c76…ddaf

0x34b655…2a6f

4 touches
1 conflict

0xd9a117fc…234a

0x34b655…2a6f

4 touches
1 conflict

0xfb4f6c11…7103

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 0x35a9f06ccf…e37689

← previous block·next block →recent activity