← previous blocknext block →recent activity

Analyzing

Block #84,048,124

17 transactions · 16 stateful · 2026-06-27 14:14:42 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,048,124  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xb30e1191…9e3c

0x34b655…2a6f

8 touches
6 conflicts

0x785889c9…0603

0x34b655…2a6f

6 touches
3 conflicts

0x29686688…0598

0xa6afd3…d132

6 touches
3 conflicts

0x0c969dde…6b06

0xa6afd3…d132

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0xe02484a6…c32e

0xc8689a…ee79

4 touches
1 conflict

0x6f6fc26c…3e34

0x34b655…2a6f

4 touches
1 conflict

0x8726ff39…3be8

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

6 conflicts on slot 0xb30e119129…4f9e3c

← previous block·next block →recent activity