← previous blocknext block →recent activity

Analyzing

Block #86,660,371

20 transactions · 15 stateful · 2026-07-09 16:38:19 UTC

Parallelism

80/100

Blocked

53%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,660,371  ·  20 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

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x7e10454f…4d9e

0xa6afd3…d132

6 touches
3 conflicts

0xb43dc900…22f2

0xa6afd3…d132

6 touches
3 conflicts

0x5b6a7552…a4b9

0x34b655…2a6f

4 touches
1 conflict

0x8b87ece6…3353

0x34b655…2a6f

4 touches
1 conflict

0xa29182a1…c12c

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

6 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity