← previous blocknext block →recent activity

Analyzing

Block #86,293,565

16 transactions · 11 stateful · 2026-07-07 23:44:20 UTC

Parallelism

88/100

Blocked

18%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,293,565  ·  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

0x8f31e46c…6caf

0x34b655…2a6f

4 touches
1 conflict

0xa070b969…42c5

0x34b655…2a6f

4 touches
1 conflict

0xa62791bc…c2ec

0x34b655…2a6f

4 touches
1 conflict

0xec0e0220…cb90

0x34b655…2a6f

4 touches
1 conflict

0xf1650392…5611

0x34b655…2a6f

4 touches
1 conflict

0xf5012b17…2996

0x34b655…2a6f

4 touches
1 conflict

0xffb8950c…23c6

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

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 0x8f31e46c6c…b06caf

← previous block·next block →recent activity