← previous blocknext block →recent activity

Analyzing

Block #83,655,062

22 transactions · 21 stateful · 2026-06-25 18:33:40 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,655,062  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x46d5a052…ff2e

0x34b655…2a6f

8 touches
6 conflicts

0xa80684c9…3948

0x34b655…2a6f

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x1c48b3ac…a03c

0x34b655…2a6f

4 touches
1 conflict

0x2297af12…c668

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x487922c6…dbd2

0x34b655…2a6f

4 touches
1 conflict

0x6ac6d1bf…8b19

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

6 conflicts on slot 0x46d5a0529d…adff2e

← previous block·next block →recent activity