← previous blocknext block →recent activity

Analyzing

Block #83,627,980

24 transactions · 18 stateful · 2026-06-25 15:32:51 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,627,980  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x8e5cc690…b06b

0x34b655…2a6f

12 touches
15 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

12 touches
15 conflicts

0x9fbabe09…8dd6

0x34b655…2a6f

12 touches
15 conflicts

0x022f72c3…07b6

0xc8689a…ee79

12 touches
15 conflicts

0x0835adb5…ad83

0x34b655…2a6f

10 touches
10 conflicts

0x758bd24b…cc0c

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x11431f9d…42c5

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

15 conflicts on slot 0x8e5cc69035…0db06b

← previous block·next block →recent activity