← previous blocknext block →recent activity

Analyzing

Block #83,452,613

25 transactions · 19 stateful · 2026-06-24 20:02:44 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

1.08

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #83,452,613  ·  25 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

0xc47ca59a…b171

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x32359294…7113

0x34b655…2a6f

4 touches
1 conflict

0x5396d712…a139

0x34b655…2a6f

4 touches
1 conflict

0x61bc3721…a8ac

0x34b655…2a6f

4 touches
1 conflict

0x6ceffbf3…4fe8

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