← previous blocknext block →recent activity

Analyzing

Block #90,326,540

18 transactions · 17 stateful · 2026-07-25 22:57:13 UTC

Parallelism

72/100

Blocked

53%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,326,540  ·  18 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

0x033cf007…136d

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea38cebb…e49e

0xd32edf…ff58

5 touches
3 conflicts

0x0921c970…9f93

0x34b655…2a6f

4 touches
1 conflict

0x193f0408…6372

0x34b655…2a6f

4 touches
1 conflict

0x213a54fa…c85f

0x34b655…2a6f

4 touches
1 conflict

0x2d651956…12e8

0x34b655…2a6f

4 touches
1 conflict

0x2ed336a4…72b1

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 0x033cf007c8…d2136d

← previous block·next block →recent activity