← previous blocknext block →recent activity

Analyzing

Block #90,439,665

7 transactions · 6 stateful · 2026-07-26 08:37:40 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,439,665  ·  7 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

0x66bdb4c2…7ea6

0x34b655…2a6f

6 touches
3 conflicts

0xdba1884a…136d

0x34b655…2a6f

4 touches
1 conflict

0x3bdd71a2…b6eb

0x34b655…2a6f

4 touches
1 conflict

0x406b11d5…326f

0x34b655…2a6f

4 touches
1 conflict

0x6a8d8180…0ae3

0x34b655…2a6f

4 touches
1 conflict

0x6c084dcb…640c

0x34b655…2a6f

4 touches
1 conflict

0x71892c70…660d

0x34b655…2a6f

4 touches
1 conflict

0x9e70dadd…810d

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 0x66bdb4c268…a97ea6

← previous block·next block →recent activity