← previous blocknext block →recent activity

Analyzing

Block #91,134,073

21 transactions · 20 stateful · 2026-07-28 18:52:26 UTC

Parallelism

76/100

Blocked

30%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,134,073  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xebac0f82…a49c

0x34b655…2a6f

6 touches
3 conflicts

0xa779293b…5e59

0x34b655…2a6f

6 touches
3 conflicts

0x0d2e1791…c1dd

0x34b655…2a6f

4 touches
1 conflict

0x2e52c539…7b18

0x34b655…2a6f

4 touches
1 conflict

0x3377da70…01e5

0x34b655…2a6f

4 touches
1 conflict

0x418f6232…2de6

0x34b655…2a6f

4 touches
1 conflict

0x41c8951d…808e

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