← previous blocknext block →recent activity

Analyzing

Block #86,443,538

17 transactions · 14 stateful · 2026-07-08 16:26:12 UTC

Parallelism

88/100

Blocked

7%

Avg conflicts / tx

0.12

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,443,538  ·  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

0xafd867b7…2b2d

0x34b655…2a6f

4 touches
1 conflict

0xafd867b7…2b2e

0x34b655…2a6f

4 touches
1 conflict

0xd19c9d38…b459

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x17792361…4d4c

0x34b655…2a6f

4 touches
1 conflict

0x1c8a3a66…2a9c

0x34b655…2a6f

4 touches
1 conflict

0x40dacbb1…d90e

0x34b655…2a6f

4 touches
1 conflict

0x782f208c…4a86

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

1 conflict on slot 0xafd867b7ed…d92b2d

← previous block·next block →recent activity