← previous blocknext block →recent activity

Analyzing

Block #90,803,432

21 transactions · 14 stateful · 2026-07-27 15:08:03 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,803,432  ·  21 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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x1d68c976…b6e6

0x34b655…2a6f

6 touches
3 conflicts

0x12978194…d32f

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x20ff72d4…5971

0x34b655…2a6f

4 touches
1 conflict

0x344bc09a…942f

0x34b655…2a6f

4 touches
1 conflict

0x47fe36d9…3b31

0x34b655…2a6f

4 touches
1 conflict

0x55cf4758…265c

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity