← previous blocknext block →recent activity

Analyzing

Block #86,487,683

21 transactions · 19 stateful · 2026-07-08 21:21:34 UTC

Parallelism

71/100

Blocked

37%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,487,683  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x22e0cc1d…ad0d

0x34b655…2a6f

12 touches
15 conflicts

0xd147ef4d…36ef

0x34b655…2a6f

10 touches
10 conflicts

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

8 touches
6 conflicts

0x7ee6007b…fd68

0x34b655…2a6f

8 touches
6 conflicts

0x9f40a209…1193

0x34b655…2a6f

8 touches
6 conflicts

0xb3cdb0da…c64f

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

15 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity