← previous blocknext block →recent activity

Analyzing

Block #83,634,394

23 transactions · 22 stateful · 2026-06-25 16:15:43 UTC

Parallelism

78/100

Blocked

36%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,634,394  ·  23 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

0xe2e45419…f17b

0x34b655…2a6f

8 touches
6 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0x8d3f06db…98cb

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0xe02484a6…c32e

0xc8689a…ee79

6 touches
3 conflicts

0x2cd889eb…ecbd

0x34b655…2a6f

6 touches
3 conflicts

0x3c5f33a0…1433

0xd32edf…ff58

5 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

6 conflicts on slot 0xe2e454194e…59f17b

← previous block·next block →recent activity