← previous blocknext block →recent activity

Analyzing

Block #82,968,223

23 transactions · 19 stateful · 2026-06-22 14:04:48 UTC

Parallelism

78/100

Blocked

37%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #82,968,223  ·  23 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

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xd45bf713…49a6

0x34b655…2a6f

6 touches
3 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

6 touches
3 conflicts

0xea83a1f2…18ce

0x34b655…2a6f

4 touches
2 conflicts

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

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

10 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity