← previous blocknext block →recent activity

Analyzing

Block #83,641,402

21 transactions · 19 stateful · 2026-06-25 17:02:32 UTC

Parallelism

81/100

Blocked

37%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,641,402  ·  21 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

0xf7468e81…86e5

0x34b655…2a6f

6 touches
3 conflicts

0x8f0e8a2f…a850

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

4 touches
1 conflict

0x9fbabe09…8dd6

0x34b655…2a6f

4 touches
1 conflict

0xa1763ef4…5892

0x34b655…2a6f

4 touches
1 conflict

0xb1c67a7d…b9b1

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 0xf7468e81f0…5b86e5

← previous block·next block →recent activity