← previous blocknext block →recent activity

Analyzing

Block #91,445,288

20 transactions · 16 stateful · 2026-07-29 21:00:21 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,445,288  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x033cf007…136d

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x08a39015…efa0

0x34b655…2a6f

6 touches
3 conflicts

0x08636046…e60f

0x34b655…2a6f

4 touches
1 conflict

0x1a005314…96d1

0x34b655…2a6f

4 touches
1 conflict

0x210b8252…1a88

0x34b655…2a6f

4 touches
1 conflict

0x28f324ed…9db7

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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 0x033cf007c8…d2136d

← previous block·next block →recent activity