← previous blocknext block →recent activity

Analyzing

Block #84,574,306

18 transactions · 14 stateful · 2026-06-30 00:41:43 UTC

Parallelism

83/100

Blocked

43%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,574,306  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xb30e1191…9e3c

0x34b655…2a6f

6 touches
3 conflicts

0xab86573c…682e

0x34b655…2a6f

6 touches
3 conflicts

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

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 0xac2a02739b…81721b

← previous block·next block →recent activity