← previous blocknext block →recent activity

Analyzing

Block #83,628,025

23 transactions · 21 stateful · 2026-06-25 15:33:10 UTC

Parallelism

74/100

Blocked

38%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,628,025  ·  23 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

12 touches
15 conflicts

0x9fbabe09…8dd6

0x34b655…2a6f

6 touches
3 conflicts

0x022f72c3…07b6

0xc8689a…ee79

6 touches
3 conflicts

0xc2ab3ad1…a6bc

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xaa7ee7…f0e4

6 touches
3 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

6 touches
3 conflicts

0xdb19247d…233c

0x34b655…2a6f

4 touches
1 conflict

0xdf9957df…8d42

0x34b655…2a6f

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

15 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity