← previous blocknext block →recent activity

Analyzing

Block #91,244,252

21 transactions · 19 stateful · 2026-07-29 04:06:40 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,244,252  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc5a1b2fe…5369

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x11f14943…6983

0x34b655…2a6f

4 touches
1 conflict

0x18e86f02…fa98

0x34b655…2a6f

4 touches
1 conflict

0x22bef947…cc48

0x34b655…2a6f

4 touches
1 conflict

0x92115abd…ad76

0x34b655…2a6f

4 touches
1 conflict

0xacd1b162…bee6

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 0xc5a1b2febf…f05369

← previous block·next block →recent activity