← previous blocknext block →recent activity

Analyzing

Block #86,619,768

24 transactions · 20 stateful · 2026-07-09 12:05:48 UTC

Parallelism

75/100

Blocked

35%

Avg conflicts / tx

0.38

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,619,768  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xb43dc900…22f2

0xa6afd3…d132

4 touches
1 conflict

0x917f9a70…3764

0x34b655…2a6f

4 touches
1 conflict

0xc0eb79d1…29a4

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xefcdf197…96a2

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 0x7aad02c682…feb979

← previous block·next block →recent activity