← previous blocknext block →recent activity

Analyzing

Block #84,044,589

30 transactions · 21 stateful · 2026-06-27 13:51:12 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #84,044,589  ·  30 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

0x62d6e82b…a750

0x34b655…2a6f

6 touches
3 conflicts

0x76477ddf…b8f8

0xc8689a…ee79

6 touches
3 conflicts

0x785889c9…0603

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x66e47d07…baa6

0x34b655…2a6f

4 touches
1 conflict

0x8e5cc690…b06b

0x34b655…2a6f

4 touches
1 conflict

0xe99d8e68…a16e

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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

3 conflicts on slot 0x62d6e82b38…66a750

← previous block·next block →recent activity