← previous blocknext block →recent activity

Analyzing

Block #90,769,396

13 transactions · 12 stateful · 2026-07-27 12:16:47 UTC

Parallelism

69/100

Blocked

33%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,769,396  ·  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

0xe8d58d34…426d

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xf2f4727d…cdb7

0x34b655…2a6f

4 touches
1 conflict

0xfc3d5171…8357

0x34b655…2a6f

4 touches
1 conflict

0x206f4379…e08a

0x34b655…2a6f

4 touches
1 conflict

0x6e5d7a21…b2fe

0x34b655…2a6f

4 touches
1 conflict

0x73aa0986…5f50

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 0xe8d58d3462…c2426d

← previous block·next block →recent activity