← previous blocknext block →recent activity

Analyzing

Block #75,479,211

28 transactions · 22 stateful · 2026-05-18 21:29:51 UTC

Parallelism

82/100

Blocked

64%

Avg conflicts / tx

0.93

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,479,211  ·  28 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

0xb818a0a3…4500

0xd32edf…ff58

9 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x99f080dc…58c1

0x34b655…2a6f

6 touches
3 conflicts

0xa7c45762…dc01

0x34b655…2a6f

6 touches
3 conflicts

0xaa3492db…3703

0x34b655…2a6f

6 touches
3 conflicts

0xd49762c9…1359

0x34b655…2a6f

6 touches
3 conflicts

0x0711ec2d…d973

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: 0xd32edf66…9fff58

10 conflicts on slot 0xb818a0a3dd…8f4500

← previous block·next block →recent activity