← previous blocknext block →recent activity

Analyzing

Block #83,669,304

21 transactions · 20 stateful · 2026-06-25 20:08:39 UTC

Parallelism

81/100

Blocked

40%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,669,304  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x1e346a85…e9c5

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0x98067f20…59e7

0x1b6862…e19c

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xbd68c7c7…40b3

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

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

3 conflicts on slot 0x1e346a85f5…1ee9c5

← previous block·next block →recent activity