← previous blocknext block →recent activity

Analyzing

Block #91,774,610

24 transactions · 21 stateful · 2026-07-31 00:37:02 UTC

Parallelism

58/100

Blocked

52%

Avg conflicts / tx

1.29

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #91,774,610  ·  24 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x2d651956…12e8

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf4f9cac7…fd98

0x34b655…2a6f

8 touches
6 conflicts

0x46346c28…1297

0x34b655…2a6f

6 touches
3 conflicts

0x4a3eff8a…16c3

0x34b655…2a6f

6 touches
3 conflicts

0x640b61a9…cda9

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x7a2c83a3…a29a

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 0x2d65195682…4112e8

← previous block·next block →recent activity