← previous blocknext block →recent activity

Analyzing

Block #83,624,442

27 transactions · 24 stateful · 2026-06-25 15:09:14 UTC

Parallelism

56/100

Blocked

54%

Avg conflicts / tx

2.22

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #83,624,442  ·  27 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

18 touches
36 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

14 touches
21 conflicts

0xffc2f21e…b393

0x34b655…2a6f

12 touches
15 conflicts

0x63c900f4…2600

0x34b655…2a6f

10 touches
10 conflicts

0x022f72c3…07b6

0xc8689a…ee79

10 touches
10 conflicts

0x4abf223d…0915

0x34b655…2a6f

9 touches
10 conflicts

0x2bc62c2a…0767

0x34b655…2a6f

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

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

36 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity