← previous blocknext block →recent activity

Analyzing

Block #88,185,126

18 transactions · 15 stateful · 2026-07-16 18:34:56 UTC

Parallelism

72/100

Blocked

53%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #88,185,126  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1c48b3ac…a03c

0x34b655…2a6f

4 touches
1 conflict

0x2a513dfb…2bb8

0x34b655…2a6f

4 touches
1 conflict

0x2f461725…5ab2

0x34b655…2a6f

4 touches
1 conflict

0x4cabb80a…46bf

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 0x326a02b5c5…5c8dad

← previous block·next block →recent activity