← previous blocknext block →recent activity

Analyzing

Block #86,633,272

24 transactions · 20 stateful · 2026-07-09 13:36:01 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,633,272  ·  24 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

0x89c7ec3b…85ba

0x34b655…2a6f

10 touches
10 conflicts

0xc0b9bd73…7f1c

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0x63c900f4…2600

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x70b87e4d…65d5

0x34b655…2a6f

8 touches
6 conflicts

0xd3ef5630…0de9

0x34b655…2a6f

8 touches
6 conflicts

0x7506443a…4820

0x34b655…2a6f

8 touches
6 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

10 conflicts on slot 0x89c7ec3b6a…8e85ba

← previous block·next block →recent activity