← previous blocknext block →recent activity

Analyzing

Block #83,356,129

21 transactions · 18 stateful · 2026-06-24 09:18:03 UTC

Parallelism

71/100

Blocked

56%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,356,129  ·  21 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

10 touches
10 conflicts

0x50f400ae…3d12

0x34b655…2a6f

8 touches
6 conflicts

0x0d35e1ad…b4d6

0x34b655…2a6f

8 touches
6 conflicts

0xf8372997…869e

0x34b655…2a6f

8 touches
6 conflicts

0x23c16bab…1018

0x34b655…2a6f

6 touches
3 conflicts

0x5d2b5661…df66

0x34b655…2a6f

6 touches
3 conflicts

0x5d75f067…ffb4

0x34b655…2a6f

6 touches
3 conflicts

0x6631b0bd…2c9f

0x34b655…2a6f

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