← previous blocknext block →recent activity

Analyzing

Block #77,482,023

23 transactions · 19 stateful · 2026-05-28 04:02:29 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #77,482,023  ·  23 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

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x9885a25f…2926

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x0a809ce1…7894

0x34b655…2a6f

6 touches
3 conflicts

0xcd87631b…ab74

0xd32edf…ff58

5 touches
3 conflicts

0x69941f7e…3b1d

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity