← previous blocknext block →recent activity

Analyzing

Block #86,679,330

18 transactions · 16 stateful · 2026-07-09 18:44:50 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,679,330  ·  18 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

0x56b5f5c0…a3ad

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0xfaef7662…f79b

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x1b374c44…96d9

0x34b655…2a6f

4 touches
1 conflict

0x459573ed…fbbe

0x34b655…2a6f

4 touches
1 conflict

0x503b3a72…f6df

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 0x56b5f5c03e…07a3ad

← previous block·next block →recent activity