← previous blocknext block →recent activity

Analyzing

Block #84,527,552

22 transactions · 17 stateful · 2026-06-29 19:29:26 UTC

Parallelism

82/100

Blocked

41%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,527,552  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x7c6d3d6d…9deb

0x34b655…2a6f

8 touches
6 conflicts

0xe02484a6…c32e

0xc8689a…ee79

6 touches
3 conflicts

0x0d2e1791…c1dd

0x34b655…2a6f

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0xf64a547c…30f6

0x34b655…2a6f

6 touches
3 conflicts

0xac128389…db06

0x34b655…2a6f

4 touches
1 conflict

0xb6e11b8f…f12b

0x34b655…2a6f

4 touches
1 conflict

0x7b9a42f7…7b88

0xa6afd3…d132

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 0x7c6d3d6daa…059deb

← previous block·next block →recent activity