← previous blocknext block →recent activity

Analyzing

Block #86,987,230

16 transactions · 15 stateful · 2026-07-11 05:02:16 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,987,230  ·  16 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

0xdd38f4e6…586c

0x34b655…2a6f

4 touches
1 conflict

0xdd38f4e6…586d

0x34b655…2a6f

4 touches
1 conflict

0xdfabfc25…d34e

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x619c81de…01b4

0x34b655…2a6f

4 touches
1 conflict

0x6a6e42c5…9438

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 0xdd38f4e69f…fd586c

← previous block·next block →recent activity