← previous blocknext block →recent activity

Analyzing

Block #90,027,137

14 transactions · 12 stateful · 2026-07-24 21:43:00 UTC

Parallelism

79/100

Blocked

17%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,027,137  ·  14 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

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xcea40325…6b39

0x34b655…2a6f

4 touches
1 conflict

0x34933aba…06e4

0x34b655…2a6f

4 touches
1 conflict

0xc2b37cdc…e470

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xb3a02eec…a23c

0x34b655…2a6f

3 touches
1 conflict

0x226ae29a…2612

0x34b655…2a6f

2 touches
0 conflicts

0x6d74089c…c836

0x34b655…2a6f

2 touches
0 conflicts

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity