← previous blocknext block →recent activity

Analyzing

Block #90,786,505

23 transactions · 19 stateful · 2026-07-27 13:42:51 UTC

Parallelism

87/100

Blocked

32%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,786,505  ·  23 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

0x281e160c…fdf2

0x34b655…2a6f

6 touches
3 conflicts

0x538f77c2…a9e7

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x89848989…0309

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641d

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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 0x281e160c10…93fdf2

← previous block·next block →recent activity