← previous blocknext block →recent activity

Analyzing

Block #86,249,958

18 transactions · 14 stateful · 2026-07-07 18:53:22 UTC

Parallelism

89/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,249,958  ·  18 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

0xcf94f773…2dae

0x34b655…2a6f

4 touches
1 conflict

0xd93edb3f…94ec

0x34b655…2a6f

4 touches
1 conflict

0x881e1bfd…009e

0x34b655…2a6f

4 touches
1 conflict

0xec0e0220…cb90

0x34b655…2a6f

4 touches
1 conflict

0xf195ad96…e0c3

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x1526b11f…8b21

0x34b655…2a6f

4 touches
1 conflict

0x52d4d54e…2c8a

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 0xcf94f7732a…5c2dae

← previous block·next block →recent activity