← previous blocknext block →recent activity

Analyzing

Block #91,973,647

25 transactions · 19 stateful · 2026-07-31 17:18:22 UTC

Parallelism

88/100

Blocked

32%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,973,647  ·  25 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xb4e0a934…5fc7

0x34b655…2a6f

6 touches
3 conflicts

0x7d9da87b…3324

0xd32edf…ff58

5 touches
3 conflicts

0xf79df061…e005

0xe52b14…7230

4 touches
1 conflict

0x21898044…a071

0x065c9d…c394

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x8b66399b…8d29

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xb9eefa49…4b83

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 0xb4e0a934b9…435fc7

← previous block·next block →recent activity