← previous blocknext block →recent activity

Analyzing

Block #86,628,831

21 transactions · 18 stateful · 2026-07-09 13:06:16 UTC

Parallelism

76/100

Blocked

39%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,628,831  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x02991b41…19e6

0x34b655…2a6f

4 touches
1 conflict

0x0a9a1df9…6b66

0x34b655…2a6f

4 touches
1 conflict

0x1dddd7ef…8f05

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x29211c1a…4115

0x34b655…2a6f

4 touches
1 conflict

0x485ae99d…f26f

0x34b655…2a6f

4 touches
1 conflict

0x636fd21a…9978

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity