← previous blocknext block →recent activity

Analyzing

Block #83,400,566

23 transactions · 21 stateful · 2026-06-24 14:15:03 UTC

Parallelism

61/100

Blocked

48%

Avg conflicts / tx

1.17

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #83,400,566  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0xffc2f21e…b393

0x34b655…2a6f

10 touches
10 conflicts

0xb6632320…a3ce

0x34b655…2a6f

9 touches
10 conflicts

0x758bd24b…cc0c

0x34b655…2a6f

8 touches
6 conflicts

0xd6071d1d…496c

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x299697af…7196

0x34b655…2a6f

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity