← previous blocknext block →recent activity

Analyzing

Block #83,652,320

24 transactions · 20 stateful · 2026-06-25 18:15:26 UTC

Parallelism

63/100

Blocked

50%

Avg conflicts / tx

1.54

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #83,652,320  ·  24 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

0x22e0cc1d…ad0d

0x34b655…2a6f

14 touches
21 conflicts

0x46d5a052…ff2e

0x34b655…2a6f

13 touches
21 conflicts

0xd164f1bc…a852

0x34b655…2a6f

8 touches
6 conflicts

0xffc2f21e…b393

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00076632…7bf7

0x34b655…2a6f

6 touches
3 conflicts

0x74fd0a9b…3aaa

0x34b655…2a6f

6 touches
3 conflicts

0x8e5cc690…b06b

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity