← previous blocknext block →recent activity

Analyzing

Block #86,617,661

28 transactions · 24 stateful · 2026-07-09 11:51:42 UTC

Parallelism

82/100

Blocked

29%

Avg conflicts / tx

0.39

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,617,661  ·  28 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

0x64aaadbf…f9f3

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ab

0xb1dbf0…c0d3

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x9365e097…ff56

0x34b655…2a6f

4 touches
1 conflict

0xa5ab7b8a…c97b

0x34b655…2a6f

4 touches
1 conflict

0xbc94dfe1…0b3d

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 0x64aaadbf0a…79f9f3

← previous block·next block →recent activity