← previous blocknext block →recent activity

Analyzing

Block #90,680,348

17 transactions · 15 stateful · 2026-07-27 04:48:51 UTC

Parallelism

53/100

Blocked

53%

Avg conflicts / tx

1.41

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #90,680,348  ·  17 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x7aad02c6…b979

0x34b655…2a6f

10 touches
10 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

10 touches
10 conflicts

0xf2f4727d…cdb7

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x40aafdd2…46da

0x34b655…2a6f

6 touches
3 conflicts

0x4a5956ef…e226

0x34b655…2a6f

6 touches
3 conflicts

0x99479bc5…3a88

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

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

10 conflicts on slot 0x7aad02c682…feb979

← previous block·next block →recent activity