← previous blocknext block →recent activity

Analyzing

Block #83,581,538

16 transactions · 12 stateful · 2026-06-25 10:22:39 UTC

Parallelism

88/100

Blocked

25%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #83,581,538  ·  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

0xa5b57630…dfce

0x34b655…2a6f

4 touches
1 conflict

0x022f72c3…07b6

0xc8689a…ee79

4 touches
1 conflict

0xe99d8e68…a16e

0x34b655…2a6f

4 touches
1 conflict

0xe64e6363…e676

0x34b655…2a6f

4 touches
1 conflict

0xd2453506…54e4

0x34b655…2a6f

4 touches
1 conflict

0x157dbfb2…4089

0x34b655…2a6f

4 touches
1 conflict

0x1f3a0388…66ce

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

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 0xa5b576307e…e3dfce

← previous block·next block →recent activity