← previous blocknext block →recent activity

Analyzing

Block #83,401,647

23 transactions · 22 stateful · 2026-06-24 14:22:16 UTC

Parallelism

78/100

Blocked

27%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,401,647  ·  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

0x015374d1…dca3

0x34b655…2a6f

8 touches
6 conflicts

0x8a1eda74…de63

0x34b655…2a6f

8 touches
6 conflicts

0xb25e703a…6ee7

0x34b655…2a6f

6 touches
3 conflicts

0xe155a04c…f267

0x34b655…2a6f

6 touches
3 conflicts

0x71632345…6ee9

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x329f2f7d…dcff

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

6 conflicts on slot 0x015374d181…9fdca3

← previous block·next block →recent activity