← previous blocknext block →recent activity

Analyzing

Block #91,977,358

24 transactions · 23 stateful · 2026-07-31 17:37:03 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,977,358  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xff196840…a453

0x34b655…2a6f

6 touches
3 conflicts

0x1f396cee…862f

0x34b655…2a6f

4 touches
1 conflict

0x42b04648…21d1

0x34b655…2a6f

4 touches
1 conflict

0x56a284d9…32e4

0x34b655…2a6f

4 touches
1 conflict

0xbd9491f7…dd92

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641f

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 0x482471adbb…39122f

← previous block·next block →recent activity