← previous blocknext block →recent activity

Analyzing

Block #91,443,789

22 transactions · 21 stateful · 2026-07-29 20:52:49 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,443,789  ·  22 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

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x08636046…e60f

0x34b655…2a6f

6 touches
3 conflicts

0x2c2db8e9…fdc7

0x34b655…2a6f

4 touches
1 conflict

0x4efae872…6aa8

0x34b655…2a6f

4 touches
1 conflict

0x62380a51…952f

0x34b655…2a6f

4 touches
1 conflict

0x63759c44…7f20

0x34b655…2a6f

4 touches
1 conflict

0x655b053e…1716

0x34b655…2a6f

4 touches
1 conflict

0x9b7e062c…de1f

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity