← previous blocknext block →recent activity

Analyzing

Block #83,628,229

25 transactions · 22 stateful · 2026-06-25 15:34:32 UTC

Parallelism

76/100

Blocked

32%

Avg conflicts / tx

0.52

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,628,229  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

6 touches
3 conflicts

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x13aceb70…cf9f

0x34b655…2a6f

5 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0x1f8a126c…9aa4

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

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

3 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity