← previous blocknext block →recent activity

Analyzing

Block #79,114,886

21 transactions · 18 stateful · 2026-06-04 17:31:42 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #79,114,886  ·  21 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

0x34a1ee7e…fb20

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xdbe2bd78…31fb

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0x0f28fb99…3d2a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x5ffc25fa…b119

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 0x34a1ee7e95…7cfb20

← previous block·next block →recent activity