← previous blocknext block →recent activity

Analyzing

Block #83,659,636

25 transactions · 21 stateful · 2026-06-25 19:04:10 UTC

Parallelism

64/100

Blocked

48%

Avg conflicts / tx

1.32

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #83,659,636  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x7527802e…2ba9

0x34b655…2a6f

10 touches
10 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x329f2f7d…dcff

0x34b655…2a6f

8 touches
6 conflicts

0xbd68c7c7…40b3

0x34b655…2a6f

8 touches
6 conflicts

0x022f72c3…07b6

0xc8689a…ee79

6 touches
3 conflicts

0x55c19be0…00a2

0x34b655…2a6f

6 touches
3 conflicts

0x9b58e20f…2dd9

0x34b655…2a6f

6 touches
3 conflicts

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 0x7527802eb9…2a2ba9

← previous block·next block →recent activity