← previous blocknext block →recent activity

Analyzing

Block #86,964,266

18 transactions · 17 stateful · 2026-07-11 02:28:53 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,964,266  ·  18 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

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x75959b84…9bda

0x34b655…2a6f

6 touches
3 conflicts

0xb652c396…b8fa

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x3cbb66ce…0e6d

0x34b655…2a6f

4 touches
1 conflict

0x4cff6c4d…f90c

0x34b655…2a6f

4 touches
1 conflict

0x4da87506…fdf1

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

3 conflicts on slot 0x0733be30d6…38112f

← previous block·next block →recent activity