← previous blocknext block →recent activity

Analyzing

Block #91,105,229

19 transactions · 14 stateful · 2026-07-28 16:27:20 UTC

Parallelism

84/100

Blocked

21%

Avg conflicts / tx

0.16

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,105,229  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x421099c9…8896

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x08381baf…6597

0x34b655…2a6f

2 touches
0 conflicts

0x12e5ded5…a9d1

0x34b655…2a6f

2 touches
0 conflicts

0x327c57dd…836d

0x34b655…2a6f

2 touches
0 conflicts

0x3e4af36e…07ae

0x34b655…2a6f

2 touches
0 conflicts

0x4777e408…acc7

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