← previous blocknext block →recent activity

Analyzing

Block #90,234,016

9 transactions · 6 stateful · 2026-07-25 15:08:38 UTC

Parallelism

78/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,234,016  ·  9 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

0x26607bc2…7fd6

0x34b655…2a6f

4 touches
1 conflict

0x37d710c8…45c1

0x34b655…2a6f

4 touches
1 conflict

0x4b76146e…0dcb

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd10ed83d…b17f

0x34b655…2a6f

4 touches
1 conflict

0xe0e2ffb5…9e33

0x34b655…2a6f

4 touches
1 conflict

0x1f3f22b1…0603

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x26607bc28d…b87fd6

← previous block·next block →recent activity