← previous blocknext block →recent activity

Analyzing

Block #83,639,602

19 transactions · 17 stateful · 2026-06-25 16:50:30 UTC

Parallelism

74/100

Blocked

41%

Avg conflicts / tx

0.84

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,639,602  ·  19 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

0xf7468e81…86e5

0x34b655…2a6f

10 touches
10 conflicts

0xd96faa58…2dde

0x34b655…2a6f

8 touches
6 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0x022f72c3…07b6

0xc8689a…ee79

6 touches
3 conflicts

0x7e6c970a…65af

0x34b655…2a6f

6 touches
3 conflicts

0xb1c67a7d…b9b1

0x34b655…2a6f

6 touches
3 conflicts

0xa9db7b4d…2957

0x40c49f…2af0

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

10 conflicts on slot 0xf7468e81f0…5b86e5

← previous block·next block →recent activity