← previous blocknext block →recent activity

Analyzing

Block #91,395,238

24 transactions · 22 stateful · 2026-07-29 16:47:18 UTC

Parallelism

75/100

Blocked

32%

Avg conflicts / tx

0.38

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,395,238  ·  24 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

0xbc66586e…20fe

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x6c26d635…1bbf

0x34b655…2a6f

4 touches
1 conflict

0xafa963d0…f7fc

0x34b655…2a6f

4 touches
1 conflict

0xb514ce62…3397

0x34b655…2a6f

4 touches
1 conflict

0xb9854153…ac42

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 0xbc66586e8f…a220fe

← previous block·next block →recent activity