← previous blocknext block →recent activity

Analyzing

Block #83,666,045

28 transactions · 24 stateful · 2026-06-25 19:46:52 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.32

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #83,666,045  ·  28 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xb6b7c45d…9d5a

0x34b655…2a6f

12 touches
15 conflicts

0x022f72c3…07b6

0xc8689a…ee79

8 touches
6 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

8 touches
6 conflicts

0x9fbabe09…8dd6

0x34b655…2a6f

8 touches
6 conflicts

0xc43aefda…e47d

0x34b655…2a6f

8 touches
6 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

21 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity