← previous blocknext block →recent activity

Analyzing

Block #91,410,397

19 transactions · 16 stateful · 2026-07-29 18:03:54 UTC

Parallelism

89/100

Blocked

19%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #91,410,397  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xb9834665…e363

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x7e1faa73…bfbf

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x2616e9ea…6ee6

0x34b655…2a6f

2 touches
0 conflicts

0x41c60d1a…8136

0x34b655…2a6f

2 touches
0 conflicts

0x5b2d25ba…eb48

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity