← previous blocknext block →recent activity

Analyzing

Block #83,356,049

25 transactions · 20 stateful · 2026-06-24 09:17:31 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

1.08

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,356,049  ·  25 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

0xe99d8e68…a16e

0x34b655…2a6f

14 touches
21 conflicts

0x9fbabe09…8dd6

0x34b655…2a6f

8 touches
6 conflicts

0xb9b4eff6…c3ef

0x34b655…2a6f

8 touches
6 conflicts

0x5d2b5661…df66

0x34b655…2a6f

8 touches
6 conflicts

0x8a01f41e…d4bf

0x34b655…2a6f

8 touches
6 conflicts

0xf06ab8d8…3589

0x34b655…2a6f

8 touches
6 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

8 touches
6 conflicts

0x18cbab19…7a73

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 0xe99d8e683a…2ea16e

← previous block·next block →recent activity