← previous blocknext block →recent activity

Analyzing

Block #91,388,087

18 transactions · 14 stateful · 2026-07-29 16:11:20 UTC

Parallelism

72/100

Blocked

57%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,388,087  ·  18 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

0xdfd3fa03…8c67

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x38bdc5d3…a632

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…004b

0x80c745…7210

6 touches
3 conflicts

0x00000000…004c

0x80c745…7210

6 touches
3 conflicts

0xef63399c…5551

0x34b655…2a6f

4 touches
1 conflict

0x7fc0a229…9d4a

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 0xdfd3fa0313…b98c67

← previous block·next block →recent activity