← previous blocknext block →recent activity

Analyzing

Block #84,509,656

19 transactions · 16 stateful · 2026-06-29 17:30:07 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,509,656  ·  19 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

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x7c6d3d6d…9deb

0x34b655…2a6f

10 touches
10 conflicts

0x11079779…7f2a

0x34b655…2a6f

8 touches
6 conflicts

0xe02484a6…c32e

0xc8689a…ee79

6 touches
3 conflicts

0x1758f935…6074

0x34b655…2a6f

6 touches
3 conflicts

0x25de453d…9573

0x34b655…2a6f

6 touches
3 conflicts

0xa6f7ec90…7bc9

0x34b655…2a6f

6 touches
3 conflicts

0xbb96f8af…205f

0x34b655…2a6f

6 touches
3 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

10 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity