← previous blocknext block →recent activity

Analyzing

Block #91,385,993

15 transactions · 15 stateful · 2026-07-29 16:00:48 UTC

Parallelism

87/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #91,385,993  ·  15 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x9cf37d01…9231

0x34b655…2a6f

4 touches
1 conflict

0xa38d4759…38d8

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd30f9e74…d404

0x34b655…2a6f

4 touches
1 conflict

0xda27c764…7fab

0x34b655…2a6f

4 touches
1 conflict

0x8d5fc820…1750

0x34b655…2a6f

4 touches
1 conflict

0x2b747f7d…4d32

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0x9cf37d01d6…a29231

← previous block·next block →recent activity