← previous blocknext block →recent activity

Analyzing

Block #90,792,761

22 transactions · 22 stateful · 2026-07-27 14:14:22 UTC

Parallelism

86/100

Blocked

27%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,792,761  ·  22 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

0x033cf007…136d

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xed28c187…4174

0x40c49f…2af0

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x76d1e78d…7877

0x40c49f…2af0

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