← previous blocknext block →recent activity

Analyzing

Block #85,904,560

19 transactions · 17 stateful · 2026-07-06 04:27:44 UTC

Parallelism

84/100

Blocked

29%

Avg conflicts / tx

0.37

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,904,560  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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…2b2e

0x34b655…2a6f

6 touches
3 conflicts

0xafd867b7…2b2d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x1517ed9b…659c

0x34b655…2a6f

4 touches
1 conflict

0xcb01e0b8…439b

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

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 0xafd867b7ed…d92b2e

← previous block·next block →recent activity