← previous blocknext block →recent activity

Analyzing

Block #89,577,938

13 transactions · 12 stateful · 2026-07-23 05:48:49 UTC

Parallelism

69/100

Blocked

42%

Avg conflicts / tx

0.77

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,577,938  ·  13 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

0x0a60413e…7178

0x34b655…2a6f

6 touches
3 conflicts

0x861e5aef…d32c

0x34b655…2a6f

6 touches
3 conflicts

0x9e70dadd…810d

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd51e027e…7c31

0x34b655…2a6f

4 touches
1 conflict

0x71892c70…660d

0x34b655…2a6f

4 touches
1 conflict

0x76641f35…47af

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 0x0a60413ee8…737178

← previous block·next block →recent activity