← previous blocknext block →recent activity

Analyzing

Block #75,128,315

14 transactions · 14 stateful · 2026-05-17 06:24:44 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.86

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,128,315  ·  14 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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x631b4113…baa9

0x34b655…2a6f

6 touches
3 conflicts

0x3e693216…fa0e

0x34b655…2a6f

4 touches
1 conflict

0x46a1bf16…f563

0x34b655…2a6f

4 touches
1 conflict

0x62d6e82b…a750

0x34b655…2a6f

4 touches
1 conflict

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0x8f5fdd0a…6c4c

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

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity