← previous blocknext block →recent activity

Analyzing

Block #91,128,173

16 transactions · 15 stateful · 2026-07-28 18:22:45 UTC

Parallelism

69/100

Blocked

47%

Avg conflicts / tx

0.69

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,128,173  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x80afd9d9…57cf

0x065c9d…c394

4 touches
1 conflict

0x01fd2f1a…f8f2

0x34b655…2a6f

4 touches
1 conflict

0x1bc07c63…d6ad

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x69ee34d1…30f8

0x34b655…2a6f

4 touches
1 conflict

0x70b7b52e…7743

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

← previous block·next block →recent activity