← previous blocknext block →recent activity

Analyzing

Block #91,423,819

26 transactions · 23 stateful · 2026-07-29 19:11:31 UTC

Parallelism

54/100

Blocked

48%

Avg conflicts / tx

1.96

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #91,423,819  ·  26 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

18 touches
36 conflicts

0xe6e6f436…ddc0

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x3661f59a…874a

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xebac0f82…a49c

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

36 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity