← previous blocknext block →recent activity

Analyzing

Block #91,961,650

19 transactions · 18 stateful · 2026-07-31 16:18:03 UTC

Parallelism

84/100

Blocked

39%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,961,650  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xf79df061…e005

0xe52b14…7230

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x56a7bac5…dbf3

0x34b655…2a6f

4 touches
1 conflict

0x6459805c…615d

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x342fbbca…d443

0x40c49f…2af0

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity