← previous blocknext block →recent activity

Analyzing

Block #91,111,143

17 transactions · 16 stateful · 2026-07-28 16:57:05 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,111,143  ·  17 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

0x217bd767…b79e

0x34b655…2a6f

8 touches
6 conflicts

0xa300902c…009e

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x25907bcb…6181

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5111cbd9…01fd

0x34b655…2a6f

4 touches
1 conflict

0x520f8a31…65c5

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 0x217bd767aa…4fb79e

← previous block·next block →recent activity