← previous blocknext block →recent activity

Analyzing

Block #75,103,134

10 transactions · 9 stateful · 2026-05-17 03:36:37 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,103,134  ·  10 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

0x438cf5f6…f077

0x2a68ba…90c5

4 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0xfebe4140…f313

0xd32edf…ff58

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x030eb8d9…44bf

0x065c9d…c394

2 touches
0 conflicts

0x288480db…a2f0

0x065c9d…c394

2 touches
0 conflicts

0x293569c1…9b4d

0x065c9d…c394

2 touches
0 conflicts

0xba38536d…2b7d

0x065c9d…c394

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x438cf5f603…8ef077

← previous block·next block →recent activity