← previous blocknext block →recent activity

Analyzing

Block #79,413,851

21 transactions · 19 stateful · 2026-06-06 02:48:51 UTC

Parallelism

81/100

Blocked

37%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #79,413,851  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf132702c…1067

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xdbc6e634…e16c

0x1b6862…e19c

4 touches
1 conflict

0x033cf007…136d

0x34b655…2a6f

4 touches
1 conflict

0xcb89a818…e7c1

0x34b655…2a6f

4 touches
1 conflict

0xeeb38aa7…8f00

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity