← previous blocknext block →recent activity

Analyzing

Block #83,629,171

20 transactions · 16 stateful · 2026-06-25 15:40:49 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.9

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,629,171  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x022f72c3…07b6

0xc8689a…ee79

8 touches
6 conflicts

0x5396d712…a139

0x34b655…2a6f

8 touches
6 conflicts

0x82dd2252…e1ce

0x34b655…2a6f

8 touches
6 conflicts

0x93641233…06f5

0x34b655…2a6f

8 touches
6 conflicts

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0xb41c8105…54ec

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

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

10 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity