← previous blocknext block →recent activity

Analyzing

Block #91,065,428

36 transactions · 32 stateful · 2026-07-28 13:07:02 UTC

Parallelism

89/100

Blocked

9%

Avg conflicts / tx

0.22

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,065,428  ·  36 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x85eb1316…bb9e

0x34b655…2a6f

6 touches
3 conflicts

0x1e737223…2278

0x34b655…2a6f

4 touches
1 conflict

0xd6255b52…69e7

0x34b655…2a6f

4 touches
1 conflict

0x8ec95f2b…f4d7

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x1408a100…f721

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity