← previous blocknext block →recent activity

Analyzing

Block #91,075,067

26 transactions · 20 stateful · 2026-07-28 13:55:31 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.85

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,075,067  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x1a287886…0266

0xa6afd3…d132

6 touches
3 conflicts

0xb409e204…89ac

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x1803586e…d149

0xa6afd3…d132

6 touches
3 conflicts

0xaf66a77e…071e

0x34b655…2a6f

5 touches
3 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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity