← previous blocknext block →recent activity

Analyzing

Block #82,977,580

21 transactions · 16 stateful · 2026-06-22 15:07:21 UTC

Parallelism

76/100

Blocked

44%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #82,977,580  ·  21 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

0xa8b18ba0…f380

0x34b655…2a6f

8 touches
6 conflicts

0x1ebe108b…72a0

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x3e505a15…70f8

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x65e661fb…d84d

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09c

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 0xa8b18ba0f2…07f380

← previous block·next block →recent activity