← previous blocknext block →recent activity

Analyzing

Block #90,485,304

13 transactions · 13 stateful · 2026-07-26 12:27:41 UTC

Parallelism

69/100

Blocked

31%

Avg conflicts / tx

0.31

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,485,304  ·  13 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

0xda27c764…7fab

0x34b655…2a6f

4 touches
1 conflict

0xeef03d6b…4375

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0fb9e50c…1a35

0x34b655…2a6f

4 touches
1 conflict

0x1408a100…f721

0x34b655…2a6f

4 touches
1 conflict

0x1bb624f3…c1b3

0x34b655…2a6f

4 touches
1 conflict

0x6254804c…a03b

0x34b655…2a6f

4 touches
1 conflict

0x6411c315…4e33

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 0xda27c76455…2e7fab

← previous block·next block →recent activity