← previous blocknext block →recent activity

Analyzing

Block #90,385,659

26 transactions · 24 stateful · 2026-07-26 04:00:06 UTC

Parallelism

85/100

Blocked

25%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,385,659  ·  26 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x64e5f38d…187c

0x34b655…2a6f

4 touches
1 conflict

0x6912341f…22c4

0x34b655…2a6f

4 touches
1 conflict

0x745952b2…d90c

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity