← previous blocknext block →recent activity

Analyzing

Block #91,421,839

17 transactions · 17 stateful · 2026-07-29 19:01:30 UTC

Parallelism

47/100

Blocked

59%

Avg conflicts / tx

1.29

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #91,421,839  ·  17 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xb9834665…e363

0x34b655…2a6f

6 touches
3 conflicts

0xe3e19268…f53b

0x34b655…2a6f

6 touches
3 conflicts

0x5502e1cc…3910

0x34b655…2a6f

6 touches
3 conflicts

0x0f2d78b1…7363

0x34b655…2a6f

6 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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity