← previous blocknext block →recent activity

Analyzing

Block #91,111,216

11 transactions · 9 stateful · 2026-07-28 16:57:27 UTC

Parallelism

73/100

Blocked

44%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,111,216  ·  11 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0f898335…7a89

0x34b655…2a6f

4 touches
1 conflict

0x3accf018…2e8b

0x34b655…2a6f

4 touches
1 conflict

0x6135a6eb…c6bb

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0x7d7ff6bb…f729

0x34b655…2a6f

4 touches
1 conflict

0x7e1faa73…bfbf

0x34b655…2a6f

4 touches
1 conflict

0x803cd43b…b348

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity