← previous blocknext block →recent activity

Analyzing

Block #89,707,401

7 transactions · 6 stateful · 2026-07-23 18:51:32 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,707,401  ·  7 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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x81561f70…fefd

0x34b655…2a6f

6 touches
3 conflicts

0x6a2ebbdd…0438

0x34b655…2a6f

4 touches
1 conflict

0x424934c8…f2f1

0x34b655…2a6f

4 touches
1 conflict

0x80656e3b…9240

0x34b655…2a6f

4 touches
1 conflict

0x842da038…b30c

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity