← previous blocknext block →recent activity

Analyzing

Block #83,412,175

27 transactions · 23 stateful · 2026-06-24 15:32:37 UTC

Parallelism

63/100

Blocked

52%

Avg conflicts / tx

1.56

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #83,412,175  ·  27 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

0x3c9bce0e…0440

0x34b655…2a6f

14 touches
21 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

14 touches
21 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

10 touches
10 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

8 touches
6 conflicts

0x5d2b5661…df66

0x34b655…2a6f

8 touches
6 conflicts

0x8e4fdba3…18f1

0x34b655…2a6f

8 touches
6 conflicts

0xb9b4eff6…c3ef

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

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 0x3c9bce0e0a…480440

← previous block·next block →recent activity