← previous blocknext block →recent activity

Analyzing

Block #88,359,112

25 transactions · 20 stateful · 2026-07-17 13:58:53 UTC

Parallelism

84/100

Blocked

35%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,359,112  ·  25 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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0x46005a44…f34b

0xa6afd3…d132

4 touches
1 conflict

0x69a491cf…abd7

0xa6afd3…d132

4 touches
1 conflict

0x26444b91…765e

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity