← previous blocknext block →recent activity

Analyzing

Block #89,596,250

14 transactions · 13 stateful · 2026-07-23 07:51:03 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,596,250  ·  14 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

0x91f687f3…aca8

0x34b655…2a6f

6 touches
3 conflicts

0x0bcbbcad…fc9c

0x34b655…2a6f

4 touches
1 conflict

0x11431f9d…42c5

0x34b655…2a6f

4 touches
1 conflict

0x30e3f228…0d43

0x34b655…2a6f

4 touches
1 conflict

0x316fa031…d758

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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 0x91f687f338…9aaca8

← previous block·next block →recent activity