← previous blocknext block →recent activity

Analyzing

Block #91,408,737

17 transactions · 14 stateful · 2026-07-29 17:55:29 UTC

Parallelism

76/100

Blocked

29%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,408,737  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x418f6232…2de6

0x34b655…2a6f

4 touches
1 conflict

0xa32a2eaa…dd84

0x34b655…2a6f

4 touches
1 conflict

0xaf151f7f…3fe4

0x34b655…2a6f

4 touches
1 conflict

0x438f088c…80b1

0x34b655…2a6f

4 touches
1 conflict

0xc864e93d…8111

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity