← previous blocknext block →recent activity

Analyzing

Block #82,742,730

21 transactions · 17 stateful · 2026-06-21 12:58:22 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #82,742,730  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd8bc53a3…c2fe

0x34b655…2a6f

8 touches
6 conflicts

0x08913286…f0df

0x34b655…2a6f

8 touches
6 conflicts

0xa1865516…fa1e

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4c99e7ce…47e4

0x34b655…2a6f

4 touches
1 conflict

0x5a19ef35…dc70

0x34b655…2a6f

4 touches
1 conflict

0x5c845558…a141

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 0xc824469a90…af6425

← previous block·next block →recent activity