← previous blocknext block →recent activity

Analyzing

Block #91,128,145

18 transactions · 16 stateful · 2026-07-28 18:22:37 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,128,145  ·  18 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

0x5cc0e9c8…3ae6

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xbc66586e…20fe

0x34b655…2a6f

4 touches
1 conflict

0xc0eb79d1…29a4

0x34b655…2a6f

4 touches
1 conflict

0xd676e291…3ecf

0x34b655…2a6f

4 touches
1 conflict

0xd9461b7e…31bc

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 0x5cc0e9c8b0…1d3ae6

← previous block·next block →recent activity