← previous blocknext block →recent activity

Analyzing

Block #91,283,393

16 transactions · 14 stateful · 2026-07-29 07:24:27 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

0.88

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,283,393  ·  16 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

0xebac0f82…a49c

0x34b655…2a6f

8 touches
6 conflicts

0x98d64054…e0f2

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xafc8de01…40dc

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x9c166a56…0356

0x34b655…2a6f

4 touches
1 conflict

0xb1e4ea6c…3e29

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 0xebac0f82ec…86a49c

← previous block·next block →recent activity