← previous blocknext block →recent activity

Analyzing

Block #91,541,494

22 transactions · 19 stateful · 2026-07-30 05:04:24 UTC

Parallelism

73/100

Blocked

42%

Avg conflicts / tx

0.91

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,541,494  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x03aa8b26…118a

0x34b655…2a6f

6 touches
3 conflicts

0x07d8b1e8…78c6

0x34b655…2a6f

6 touches
3 conflicts

0xa832a461…ee2c

0x34b655…2a6f

6 touches
3 conflicts

0xa8cff7bf…d80f

0x34b655…2a6f

6 touches
3 conflicts

0x08cc68a2…2a59

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x033cf007…136d

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x03aa8b260f…60118a

← previous block·next block →recent activity