← previous blocknext block →recent activity

Analyzing

Block #91,269,529

16 transactions · 15 stateful · 2026-07-29 06:14:22 UTC

Parallelism

75/100

Blocked

53%

Avg conflicts / tx

0.88

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,269,529  ·  16 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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6426

0x34b655…2a6f

4 touches
1 conflict

0x1bf8d2af…d140

0x34b655…2a6f

4 touches
1 conflict

0xd676e291…3ecf

0x34b655…2a6f

4 touches
1 conflict

0x344e8445…447f

0x34b655…2a6f

4 touches
1 conflict

0xf79df061…e005

0xe52b14…7230

4 touches
1 conflict

0xbcbf5d09…8bac

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity