← previous blocknext block →recent activity

Analyzing

Block #83,029,033

20 transactions · 18 stateful · 2026-06-22 20:51:41 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,029,033  ·  20 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

0x36a49c16…89b9

0xc8689a…ee79

8 touches
6 conflicts

0x08913286…f0df

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

8 touches
6 conflicts

0x98d58911…19f2

0x34b655…2a6f

8 touches
6 conflicts

0xf7e84d35…ad5c

0x34b655…2a6f

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x45e2c42e…d29a

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: Settlement / Helper

6 conflicts on slot 0x36a49c163e…f789b9

← previous block·next block →recent activity