← previous blocknext block →recent activity

Analyzing

Block #91,569,531

18 transactions · 15 stateful · 2026-07-30 07:25:25 UTC

Parallelism

89/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #91,569,531  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xf61165ef…adb9

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x91855e…ac7e

4 touches
1 conflict

0x1ed748d8…d530

0x34b655…2a6f

2 touches
0 conflicts

0x26bcd08c…8b42

0x34b655…2a6f

2 touches
0 conflicts

0x3e8569e7…04d7

0x34b655…2a6f

2 touches
0 conflicts

0x5a791b24…0e2b

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity