← previous blocknext block →recent activity

Analyzing

Block #86,610,433

23 transactions · 20 stateful · 2026-07-09 11:03:29 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,610,433  ·  23 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x1629a29f…4701

0x34b655…2a6f

6 touches
3 conflicts

0x9966da31…0d0f

0x34b655…2a6f

6 touches
3 conflicts

0xb0bc3bf8…e2b1

0x34b655…2a6f

6 touches
3 conflicts

0xedcf2991…8551

0x34b655…2a6f

6 touches
3 conflicts

0xf324b405…ca30

0x34b655…2a6f

6 touches
3 conflicts

0xf7e59d30…11dd

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

← previous block·next block →recent activity