← previous blocknext block →recent activity

Analyzing

Block #90,525,789

22 transactions · 20 stateful · 2026-07-26 15:51:19 UTC

Parallelism

73/100

Blocked

35%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,525,789  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xabfb6289…f23b

0x34b655…2a6f

8 touches
6 conflicts

0xef3f5637…f47c

0x34b655…2a6f

8 touches
6 conflicts

0x7a2c83a3…a29a

0x34b655…2a6f

8 touches
6 conflicts

0xef1de905…0582

0x34b655…2a6f

6 touches
3 conflicts

0x109d8a52…a7b7

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

15 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity