← previous blocknext block →recent activity

Analyzing

Block #83,660,100

21 transactions · 15 stateful · 2026-06-25 19:07:15 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #83,660,100  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x37a276a3…673f

0x34b655…2a6f

6 touches
3 conflicts

0xbd68c7c7…40b3

0x34b655…2a6f

6 touches
3 conflicts

0x43d16f2c…afaf

0x34b655…2a6f

4 touches
1 conflict

0x79e62da8…efdc

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe99d8e68…a16e

0x34b655…2a6f

4 touches
1 conflict

0xf3a047d3…c218

0x34b655…2a6f

4 touches
1 conflict

0x41d3bfa5…523e

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 0x37a276a33f…0f673f

← previous block·next block →recent activity