← previous blocknext block →recent activity

Analyzing

Block #83,670,385

26 transactions · 19 stateful · 2026-06-25 20:15:50 UTC

Parallelism

77/100

Blocked

37%

Avg conflicts / tx

0.46

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,670,385  ·  26 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

0x99ee776a…053a

0x34b655…2a6f

6 touches
3 conflicts

0xec0e0220…cb90

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xda7f9bd2…e332

0x34b655…2a6f

6 touches
3 conflicts

0x5aed1bd2…7afa

0x34b655…2a6f

4 touches
1 conflict

0x62d6e82b…a750

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x732229e0…aa56

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 0x99ee776a78…65053a

← previous block·next block →recent activity