← previous blocknext block →recent activity

Analyzing

Block #83,665,983

22 transactions · 19 stateful · 2026-06-25 19:46:28 UTC

Parallelism

64/100

Blocked

53%

Avg conflicts / tx

1.59

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #83,665,983  ·  22 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

0xe99d8e68…a16e

0x34b655…2a6f

14 touches
21 conflicts

0x1c48b3ac…a03c

0x34b655…2a6f

12 touches
15 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

10 touches
10 conflicts

0x200affbb…a5fb

0x34b655…2a6f

8 touches
6 conflicts

0xe02484a6…c32e

0xc8689a…ee79

6 touches
3 conflicts

0x0cdf9369…5331

0x34b655…2a6f

6 touches
3 conflicts

0xdd3f5334…09ea

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

21 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity