← previous blocknext block →recent activity

Analyzing

Block #91,295,989

21 transactions · 21 stateful · 2026-07-29 08:27:50 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,295,989  ·  21 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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xdfb97a89…abc8

0x34b655…2a6f

6 touches
3 conflicts

0xfd42a6b9…4c81

0x34b655…2a6f

6 touches
3 conflicts

0x143556cd…07a5

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5af098c7…4806

0x34b655…2a6f

4 touches
1 conflict

0x5af098c7…4807

0x34b655…2a6f

4 touches
1 conflict

0x7b67f6cf…0aab

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity