← previous blocknext block →recent activity

Analyzing

Block #90,038,610

14 transactions · 14 stateful · 2026-07-24 22:40:44 UTC

Parallelism

86/100

Blocked

21%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,038,610  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x4329bae0…29f9

0x34b655…2a6f

4 touches
1 conflict

0x93ecee58…010a

0x34b655…2a6f

4 touches
1 conflict

0x330df1e6…7587

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xb5f244d5…f550

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xe6e6f436…ddc0

0x34b655…2a6f

4 touches
1 conflict

0x160f117d…8e90

0x065c9d…c394

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

1 conflict on slot 0x4329bae0a7…f429f9

← previous block·next block →recent activity