← previous blocknext block →recent activity

Analyzing

Block #90,025,466

9 transactions · 7 stateful · 2026-07-24 21:34:33 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,025,466  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x0aa5e418…5d1d

0x34b655…2a6f

2 touches
0 conflicts

0x330df1e6…7587

0x34b655…2a6f

2 touches
0 conflicts

0x363a4317…87d2

0x34b655…2a6f

2 touches
0 conflicts

0x388633a0…86cd

0x34b655…2a6f

2 touches
0 conflicts

0x3d158563…8713

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity