← previous blocknext block →recent activity

Analyzing

Block #86,659,529

29 transactions · 19 stateful · 2026-07-09 16:32:43 UTC

Parallelism

86/100

Blocked

42%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,659,529  ·  29 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ab

0xb1dbf0…c0d3

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1aa

0xb1dbf0…c0d3

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xe3a15054…ed11

0x34b655…2a6f

6 touches
3 conflicts

0x6c3985ef…450c

0x34b655…2a6f

6 touches
3 conflicts

0xad862891…5d02

0x34b655…2a6f

6 touches
3 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

6 conflicts on slot 0x92385428ad…dc6941

← previous block·next block →recent activity