← previous blocknext block →recent activity

Analyzing

Block #83,692,036

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

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,692,036  ·  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

0x206fb8db…a146

0x34b655…2a6f

6 touches
3 conflicts

0x8b305a3b…1c35

0x34b655…2a6f

6 touches
3 conflicts

0x1175233a…64e7

0x34b655…2a6f

4 touches
1 conflict

0x1b2c54a1…5a76

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x2c75ca93…a569

0x34b655…2a6f

4 touches
1 conflict

0x31b21e64…c21c

0x34b655…2a6f

4 touches
1 conflict

0x3e505a15…70f8

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

3 conflicts on slot 0x206fb8db95…b8a146

← previous block·next block →recent activity