← previous blocknext block →recent activity

Analyzing

Block #83,624,756

22 transactions · 19 stateful · 2026-06-25 15:11:20 UTC

Parallelism

50/100

Blocked

58%

Avg conflicts / tx

1.82

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #83,624,756  ·  22 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xb6632320…a3ce

0x34b655…2a6f

10 touches
10 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

10 touches
10 conflicts

0x022f72c3…07b6

0xc8689a…ee79

10 touches
10 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

10 touches
10 conflicts

0x9fbabe09…8dd6

0x34b655…2a6f

10 touches
10 conflicts

0x63c900f4…2600

0x34b655…2a6f

8 touches
6 conflicts

0xffc2f21e…b393

0x34b655…2a6f

8 touches
6 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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity