← previous blocknext block →recent activity

Analyzing

Block #82,757,235

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

Parallelism

84/100

Blocked

37%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #82,757,235  ·  25 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

6 touches
3 conflicts

0x9ff176a9…152e

0x065c9d…c394

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xdc921364…4680

0x34b655…2a6f

6 touches
3 conflicts

0xb3c96942…f0fc

0x34b655…2a6f

6 touches
3 conflicts

0xd4726587…6289

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity