← previous blocknext block →recent activity

Analyzing

Block #83,466,665

25 transactions · 19 stateful · 2026-06-24 21:36:38 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,466,665  ·  25 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x0f28fb99…3d29

0x1b6862…e19c

4 touches
1 conflict

0x006c3b86…59a9

0x34b655…2a6f

4 touches
1 conflict

0x00966e54…7d1d

0x34b655…2a6f

4 touches
1 conflict

0x126a0344…4465

0x34b655…2a6f

4 touches
1 conflict

0x16dce2e7…6f05

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity