← previous blocknext block →recent activity

Analyzing

Block #85,806,586

18 transactions · 17 stateful · 2026-07-05 17:35:13 UTC

Parallelism

72/100

Blocked

41%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,806,586  ·  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

0x06c59b8c…89c0

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x9ff176a9…152e

0x065c9d…c394

4 touches
1 conflict

0xc88f593e…5d93

0x336ed4…c59c

4 touches
1 conflict

0x077d58c3…8ed7

0x34b655…2a6f

4 touches
1 conflict

0x0ab54c30…b88e

0x34b655…2a6f

4 touches
1 conflict

0x15f906b5…1dfc

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

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 0x06c59b8c41…2989c0

← previous block·next block →recent activity