← previous blocknext block →recent activity

Analyzing

Block #83,632,120

24 transactions · 22 stateful · 2026-06-25 16:00:31 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

1.38

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #83,632,120  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x6ca8bab1…3957

0x34b655…2a6f

14 touches
21 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

12 touches
15 conflicts

0x5396d712…a139

0x34b655…2a6f

10 touches
10 conflicts

0x82dd2252…e1ce

0x34b655…2a6f

10 touches
10 conflicts

0x022f72c3…07b6

0xc8689a…ee79

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0x69017fce…85be

0x1b6862…e19c

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

21 conflicts on slot 0x6ca8bab118…113957

← previous block·next block →recent activity