← previous blocknext block →recent activity

Analyzing

Block #86,361,563

17 transactions · 14 stateful · 2026-07-08 07:18:29 UTC

Parallelism

88/100

Blocked

14%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,361,563  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x26a95e66…d6f4

0x34b655…2a6f

2 touches
0 conflicts

0x74fd0a9b…3aaa

0x34b655…2a6f

2 touches
0 conflicts

0x77129877…f866

0x34b655…2a6f

2 touches
0 conflicts

0x7ea6a117…f2f2

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity