← previous blocknext block →recent activity

Analyzing

Block #83,638,149

23 transactions · 20 stateful · 2026-06-25 16:40:50 UTC

Parallelism

65/100

Blocked

55%

Avg conflicts / tx

1.26

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #83,638,149  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

14 touches
21 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0xfebf4166…9bf2

0x34b655…2a6f

8 touches
6 conflicts

0x31aa2853…8dbb

0xc8689a…ee79

8 touches
6 conflicts

0x4ec9ff52…e6f7

0x34b655…2a6f

8 touches
6 conflicts

0x7534f53d…6ed4

0x34b655…2a6f

6 touches
3 conflicts

0x75291f8b…3ac0

0x34b655…2a6f

4 touches
1 conflict

0x8496dbd7…3167

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

21 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity