← previous blocknext block →recent activity

Analyzing

Block #83,621,887

23 transactions · 20 stateful · 2026-06-25 14:52:09 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,621,887  ·  23 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

0xffc2f21e…b393

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x03e24ec6…4a23

0x34b655…2a6f

6 touches
3 conflicts

0x751ea1ce…c918

0x34b655…2a6f

4 touches
1 conflict

0x8a7af3fd…72a6

0x34b655…2a6f

4 touches
1 conflict

0x8e5cc690…b06b

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0x9fbabe09…8dd6

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 0xffc2f21efe…ecb393

← previous block·next block →recent activity