← previous blocknext block →recent activity

Analyzing

Block #91,235,425

19 transactions · 19 stateful · 2026-07-29 03:22:16 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.79

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,235,425  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0a0cecef…4ed0

0x34b655…2a6f

8 touches
6 conflicts

0xab7752a0…3177

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x28ceceef…ecc2

0x34b655…2a6f

6 touches
3 conflicts

0x6925548b…81cb

0x34b655…2a6f

4 touches
1 conflict

0x6925548b…81cc

0x34b655…2a6f

4 touches
1 conflict

0xa1237636…d366

0x34b655…2a6f

4 touches
1 conflict

0xa3ff1ab2…8ae3

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 0x0a0cecef55…324ed0

← previous block·next block →recent activity