← previous blocknext block →recent activity

Analyzing

Block #91,135,264

27 transactions · 23 stateful · 2026-07-28 18:58:25 UTC

Parallelism

81/100

Blocked

30%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,135,264  ·  27 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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xbc66586e…20fe

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xe1b6b3c8…6676

0x34b655…2a6f

6 touches
3 conflicts

0x198f3a22…7aeb

0x34b655…2a6f

6 touches
3 conflicts

0x4c0627bd…f5c3

0x34b655…2a6f

6 touches
3 conflicts

0x4c0627bd…f5c4

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity