← previous blocknext block →recent activity

Analyzing

Block #75,513,007

16 transactions · 11 stateful · 2026-05-19 01:21:42 UTC

Parallelism

81/100

Blocked

36%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,513,007  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x4c20d376…0819

0x34b655…2a6f

4 touches
1 conflict

0x00000000…006f

0x1efe02…37d6

2 touches
0 conflicts

0x6c2c499c…f9cc

0x1efe02…37d6

2 touches
0 conflicts

0x9250ec46…1329

0x1efe02…37d6

2 touches
0 conflicts

0xa5a6f1ab…8573

0x1efe02…37d6

2 touches
0 conflicts

0x00bac013…a28c

0x91b81b…6d56

2 touches
0 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: 0x34b6552d…112a6f

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity