← previous blocknext block →recent activity

Analyzing

Block #91,189,469

15 transactions · 13 stateful · 2026-07-28 23:31:06 UTC

Parallelism

80/100

Blocked

54%

Avg conflicts / tx

0.6

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,189,469  ·  15 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x0110331c…b891

0x34b655…2a6f

6 touches
3 conflicts

0x439cfb2c…7b9e

0xa6afd3…d132

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x4d5053d1…3b7d

0x34b655…2a6f

4 touches
1 conflict

0xb562816e…1ccd

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641e

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

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity