← previous blocknext block →recent activity

Analyzing

Block #86,628,670

19 transactions · 18 stateful · 2026-07-09 13:05:12 UTC

Parallelism

79/100

Blocked

39%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,628,670  ·  19 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

0x8388eab6…83ff

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x311ba79a…ac61

0x34b655…2a6f

6 touches
3 conflicts

0x485ae99d…f26f

0x34b655…2a6f

6 touches
3 conflicts

0x63c900f4…2600

0x34b655…2a6f

6 touches
3 conflicts

0x6a023a3d…c184

0x34b655…2a6f

6 touches
3 conflicts

0x6b2ba712…0214

0x34b655…2a6f

6 touches
3 conflicts

0x727fbce7…0c80

0x34b655…2a6f

6 touches
3 conflicts

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 0x8388eab63f…1e83ff

← previous block·next block →recent activity