← previous blocknext block →recent activity

Analyzing

Block #79,250,189

20 transactions · 15 stateful · 2026-06-05 08:34:00 UTC

Parallelism

80/100

Blocked

47%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #79,250,189  ·  20 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

0xdf708ee7…1fcf

0xc8689a…ee79

6 touches
3 conflicts

0xfb4cb196…8c4a

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x40970e69…da50

0x69df8a…6292

6 touches
3 conflicts

0x8cf3d245…1d0d

0x69df8a…6292

6 touches
3 conflicts

0xb05cd4f5…73d0

0x69df8a…6292

6 touches
3 conflicts

0xdb067026…9eb8

0x69df8a…6292

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

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: Settlement / Helper

3 conflicts on slot 0xdf708ee738…d51fcf

← previous block·next block →recent activity