← previous blocknext block →recent activity

Analyzing

Block #91,423,512

15 transactions · 15 stateful · 2026-07-29 19:09:56 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

0.93

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,423,512  ·  15 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xc2775c92…702a

0x34b655…2a6f

6 touches
3 conflicts

0xefcdf197…96a2

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x3280f198…a541

0x34b655…2a6f

4 touches
1 conflict

0x3601aa45…29cb

0x34b655…2a6f

4 touches
1 conflict

0x363f99e4…32c8

0x34b655…2a6f

4 touches
1 conflict

0x3f85f288…7c97

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity