← previous blocknext block →recent activity

Analyzing

Block #83,655,554

24 transactions · 19 stateful · 2026-06-25 18:36:57 UTC

Parallelism

79/100

Blocked

42%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,655,554  ·  24 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

0xa0c6e179…a103

0x34b655…2a6f

6 touches
3 conflicts

0x0b16149e…7d4d

0x065c9d…c394

6 touches
3 conflicts

0xff96dc9b…93d7

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf06c2cf5…61bd

0x34b655…2a6f

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x8565896d…68ef

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…002c

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

3 conflicts on slot 0xa0c6e1796c…01a103

← previous block·next block →recent activity