← previous blocknext block →recent activity

Analyzing

Block #90,808,266

18 transactions · 17 stateful · 2026-07-27 15:32:22 UTC

Parallelism

78/100

Blocked

53%

Avg conflicts / tx

0.72

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,808,266  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x1bee5aea…5f61

0x34b655…2a6f

4 touches
1 conflict

0x55955f0b…6085

0x34b655…2a6f

4 touches
1 conflict

0x57330c5d…9973

0x34b655…2a6f

4 touches
1 conflict

0x5e4b65e1…ebe1

0x34b655…2a6f

4 touches
1 conflict

0x6bdb9869…7558

0x34b655…2a6f

4 touches
1 conflict

0x747f609d…1555

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