← previous blocknext block →recent activity

Analyzing

Block #90,300,440

13 transactions · 13 stateful · 2026-07-25 20:44:34 UTC

Parallelism

85/100

Blocked

31%

Avg conflicts / tx

0.31

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,300,440  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc4ca986e…4e06

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xe3471350…0bcf

0x34b655…2a6f

4 touches
1 conflict

0xfecb18c0…01ed

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x211c747b…db9b

0x34b655…2a6f

4 touches
1 conflict

0x6939e474…4256

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

1 conflict on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity